 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| 32-bit tx system risc tx39 family TMPR3911/3912 www.datasheet.in
mips16, application specific extensions and r3000a are a trademark of mips technologies, inc. the information contained herein is subject to change without notice. the information contained herein is presented only as a guide for the applications of our products. no responsibility is assumed by toshiba for any infringements of patents or other rights of the third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of toshiba or others. the products described in this document contain components made in the united states and subject to export control of the u.s. authorities. diversion contrary to the u.s. law is prohibited. toshiba is continually working to improve the quality and reliability of its products. nevertheless, semiconductor devices in general can malfunction or fail due to their inherent electrical sensitivity and vulnerability to physical stress. it is the responsibility of the buyer, when utilizing toshiba products, to comply with the standards of safety in making a safe design for the entire system, and to avoid situations in which a malfunction or failure of such toshiba products could cause loss of human life, bodily injury or damage to property. in developing your designs, please ensure that toshiba products are used within specified operating ranges as set forth in the most recent toshiba products specifications. also, please keep in mind the precautions and conditions set forth in the ?handling guide for semiconductor devices,? or ?toshiba semiconductor reliability handbook? etc.. the toshiba products listed in this document are intended for usage in general electronics applications ( computer, personal equipment, office equipment, measuring equipment, industrial robotics, domestic appliances, etc.). these toshiba products are neither intended nor warranted for usage in equipment that requires extraordinarily high quality and/or reliability or a malfunction or failure of which may cause loss of human life or bodily injury (?unintended usage?). unintended usage include atomic energy control instruments, airplane or spaceship instruments, transportation instruments, traffic signal instruments, combustion control instruments, medical instruments, all types of safety devices, etc.. unintended usage of toshiba products listed in this document shall be made at the customer?s own risk. the products described in this document may include products subject to the foreign exchange and foreign trade laws. ? 2003 toshiba corporation all rights reserved www.datasheet.in preface thank you for choosing toshiba semiconductor products. this is the 2000 edition of the databook for the TMPR3911/12 32-bit tx system risc microprocessor. this databook is designed to be easily understood by engineers who are designing the toshiba TMPR3911/12 risc microprocessor into their products for the first time. no special knowledge of this device is assumed ? the contents includes basic information about the microprocessor and the application fields in which it is used. in addition, complete technical specifications are given, facilitating incorporation of the device into any given user application. toshiba are continually updating technical publications. any comments and suggestions regarding any toshiba document are most welcome and will be taken into account when subsequent editions are prepared. to receive updates to the information in this databook, or for additional information about the products described in it, please contact your nearest toshiba office or authorized toshiba dealer. august 2003 www.datasheet.in www.datasheet.in table of contents i table of contents handling precautions TMPR3911/12 1. TMPR3911/12 overview ......................................................................................................... ...............................1-1 1.1 overview .................................................................................................................... ....................................1-1 1.2 references .................................................................................................................. ..................................1-11 2. pin descriptions ............................................................................................................. .........................................2-1 2.1 overview .................................................................................................................... ....................................2-1 2.2 pins ........................................................................................................................ .........................................2-2 2.2.1 memory pins ............................................................................................................... ............................2-2 2.2.2 bus arbitration pins ...................................................................................................... ..........................2-6 2.2.3 clock pins ................................................................................................................ ...............................2-6 2.2.4 chi pins .................................................................................................................. ................................2-7 2.2.5 io pins................................................................................................................... ..................................2-7 2.2.6 magicbus pins ............................................................................................................. ............................2-8 2.2.7 reset pins ................................................................................................................ ................................2-8 2.2.8 power module pins ......................................................................................................... ........................2-9 2.2.9 sib pins.................................................................................................................. ...............................2-10 2.2.10 spi pins ................................................................................................................. ................................2-11 2.2.11 uart and ir pins......................................................................................................... ........................2-11 2.2.12 video pins ............................................................................................................... ..............................2-12 2.2.13 endian pin ............................................................................................................... ..............................2-13 2.2.14 test pins ................................................................................................................ ................................2-13 2.2.15 spare pins............................................................................................................... ...............................2-13 2.2.16 power supply pins ........................................................................................................ ........................2-13 2.3 pin mode .................................................................................................................... ..................................2-14 2.4 pin assignment.............................................................................................................. ...............................2-20 2.4.1 pin assignment (in case of tmpr3912au-92 and tmpr3912xb-92)................................................2-20 2.4.2 pin assignment (in case of TMPR3911bu) .................................................................................... .....2-23 2.4.3 pin assignment (in case of TMPR3911bxb)................................................................................... ....2-25 2.4.4 TMPR3911bu pin assignment ................................................................................................. ...........2-27 2.4.5 tmpr3912au-92............................................................................................................. ....................2-28 2.4.6 TMPR3911bxb ball assignment ............................................................................................... .........2-29 2.4.7 tmpr3912xb-92 ............................................................................................................. ....................2-30 3. cpu module................................................................................................................... .........................................3-1 3.1 overview .................................................................................................................... ....................................3-1 3.2 cpu core.................................................................................................................... ....................................3-2 3.2.1 description ............................................................................................................... ...............................3-2 3.3 cpu interface ............................................................................................................... ..................................3-3 3.3.1 block diagram ............................................................................................................. ...........................3-3 3.3.2 write buffer .............................................................................................................. ..............................3-4 3.3.3 interface controller ...................................................................................................... ...........................3-4 3.3.4 dma arbitration........................................................................................................... ..........................3-6 3.3.5 cpu stop mode ............................................................................................................. .........................3-6 3.3.6 tlb ....................................................................................................................... ..................................3-7 4. biu module................................................................................................................... ..........................................4-1 www.datasheet.in table of contents ii 4.1 overview .................................................................................................................... ....................................4-1 4.1.1 block diagram ............................................................................................................. ...........................4-2 4.2 address decoder............................................................................................................. ................................4-3 4.2.1 system address map........................................................................................................ .......................4-3 4.2.2 address generation ........................................................................................................ .........................4-5 4.2.3 address re-mapper logic ................................................................................................... ...................4-6 4.3 chip select controller ...................................................................................................... ..............................4-7 4.3.1 description ............................................................................................................... ...............................4-7 4.3.2 access mapping ............................................................................................................ ..........................4-8 4.3.3 cs3-cs0 and mcs3-mcs0 timing .............................................................................................. .......4-17 4.4.4 card 2 and card 1 ......................................................................................................... ........................4-20 4.4.5 cs0 size configuration.................................................................................................... .....................4-23 4.4 dram and sdram controller ................................................................................................... ................4-24 4.4.1 memory chips supported .................................................................................................... .................4-24 4.4.2 dram and sdram configurations ............................................................................................. .......4-25 4.4.3 dram...................................................................................................................... .............................4-26 4.4.4 sdram..................................................................................................................... ............................4-29 4.5 arbitration ................................................................................................................. ...................................4-32 4.5.1 refresh controller ........................................................................................................ .........................4-32 4.5.2 external bus master ....................................................................................................... .......................4-32 4.5.3 watch dog timer ........................................................................................................... .......................4-33 4.5.4 memory power down ......................................................................................................... ..................4-33 4.6 memory connections .......................................................................................................... .........................4-35 4.7 biu registers ............................................................................................................... ................................4-44 4.7.1 memory configuration 0 register ........................................................................................... .............4-44 4.7.2 memory configuration 1 register ........................................................................................... .............4-47 4.7.3 memory configuration 2 register ........................................................................................... .............4-48 4.7.4 memory configuration 3 register ........................................................................................... .............4-49 4.7.5 memory configuration 4 register ........................................................................................... .............4-51 4.7.6 memory configuration 5 register ........................................................................................... .............4-53 4.7.7 memory configuration 6 register ........................................................................................... .............4-54 4.7.8 memory configuration 7 register ........................................................................................... .............4-54 4.7.9 memory configuration 8 register ........................................................................................... .............4-54 5. siu module ................................................................................................................... ..........................................5-1 5.1 overview .................................................................................................................... ....................................5-1 5.2 implementation.............................................................................................................. .................................5-2 5.2.1 block diagram ............................................................................................................. ...........................5-2 5.2.2 dma controller description................................................................................................ ...................5-3 5.2.3 address decoder description............................................................................................... ...................5-4 5.2.4 internal function registers ............................................................................................... ......................5-5 5.3 siu registers............................................................................................................... ...................................5-7 5.3.1 siu test register ......................................................................................................... ...........................5-7 5.3.2 TMPR3911/12 revision register............................................................................................. ...............5-7 6. clock module ................................................................................................................. .........................................6-1 6.1 overview .................................................................................................................... ....................................6-1 6.1.1 related pins.............................................................................................................. ...............................6-2 6.2 implementation.............................................................................................................. .................................6-3 6.2.1 block diagram ............................................................................................................. ...........................6-3 www.datasheet.in table of contents iii 6.2.2 clock module description .................................................................................................. ....................6-5 6.3 clock registers............................................................................................................. ..................................6-6 6.3.1 clock control register.................................................................................................... ........................6-6 7. chi module................................................................................................................... ..........................................7-1 7.1 overview .................................................................................................................... ....................................7-1 7.1.1 related pins.............................................................................................................. ...............................7-1 7.2 interface requirements...................................................................................................... .............................7-2 7.2.1 frame structure and serial timing ......................................................................................... ................7-2 7.2.2 configurations............................................................................................................ .............................7-7 7.3 implementation.............................................................................................................. .................................7-8 7.3.1 block diagram ............................................................................................................. ...........................7-8 7.3.2 transmitter ............................................................................................................... ...............................7-9 7.3.3 receiver.................................................................................................................. .................................7-9 7.3.4 clock and control generation.............................................................................................. .................7-10 7.3.5 dma address generation.................................................................................................... .................7-12 7.3.6 related interrupts ........................................................................................................ ..........................7-14 7.4 chi registers ............................................................................................................... ................................7-15 7.4.1 chi control register ...................................................................................................... ......................7-15 7.4.2 chi pointer enable register ............................................................................................... ..................7-18 7.4.3 chi receive pointer a register ............................................................................................ ...............7-20 7.4.4 chi receive pointer b register............................................................................................ ................7-21 7.4.5 chi transmit pointer a register ........................................................................................... ...............7-22 7.4.6 chi transmit pointer b register ........................................................................................... ...............7-23 7.4.7 chi size register......................................................................................................... .........................7-24 7.4.8 chi rx start register..................................................................................................... ......................7-25 7.4.9 chi tx start register..................................................................................................... ......................7-25 7.4.10 chi tx holding register .................................................................................................. ...................7-26 7.4.11 chi rx holding register .................................................................................................. ...................7-26 8. interrupt module............................................................................................................. .........................................8-1 8.1 overview .................................................................................................................... ....................................8-1 8.2 implementation.............................................................................................................. .................................8-2 8.2.1 block diagram ............................................................................................................. ...........................8-2 8.2.2 interrupt logic description ............................................................................................... ......................8-3 8.3 interrupt registers ......................................................................................................... .................................8-5 8.3.1 interrupt status 1 register............................................................................................... ........................8-5 8.3.2 interrupt status 2 register............................................................................................... ........................8-8 8.3.3 interrupt status 3 register............................................................................................... ......................8-11 8.3.4 interrupt status 4 register............................................................................................... ......................8-11 8.3.5 interrupt status 5 register............................................................................................... ......................8-12 8.3.6 interrupt status 6 register............................................................................................... ......................8-15 8.3.7 clear interrupt 1 register ................................................................................................ ......................8-16 8.3.8 clear interrupt 2 register ................................................................................................ ......................8-16 8.3.9 clear interrupt 3 register ................................................................................................ ......................8-16 8.3.10 clear interrupt 4 register ............................................................................................... .......................8-16 8.3.11 clear interrupt 5 register ............................................................................................... .......................8-16 8.3.12 enable interrupt 1 register.............................................................................................. ......................8-16 8.3.13 enable interrupt 2 register.............................................................................................. ......................8-17 8.3.14 enable interrupt 3 register.............................................................................................. ......................8-17 www.datasheet.in table of contents iv 8.3.15 enable interrupt 4 register.............................................................................................. ......................8-17 8.3.16 enable interrupt 5 register.............................................................................................. ......................8-17 8.3.17 enable interrupt 6 register.............................................................................................. ......................8-18 9. i/o module ................................................................................................................... ...........................................9-1 9.1 overview .................................................................................................................... ....................................9-1 9.1.1 related pins.............................................................................................................. ...............................9-1 9.2 implementation.............................................................................................................. .................................9-2 9.2.1 block diagram ............................................................................................................. ...........................9-2 9.2.2 general purpose i/o ports................................................................................................. ......................9-4 9.2.3 multi-function i/o ports.................................................................................................. ........................9-5 9.2.4 related interrupts ........................................................................................................ ............................9-8 9.3 i/o registers ............................................................................................................... ....................................9-9 9.3.1 i/o control register ...................................................................................................... ..........................9-9 9.3.2 mfio data output register ................................................................................................. .................9-10 9.3.3 mfio direction register ................................................................................................... ...................9-10 9.3.4 mfio data input register.................................................................................................. ...................9-10 9.3.5 mfio select register...................................................................................................... ......................9-11 9.3.6 i/o power-down register ................................................................................................... ..................9-11 9.3.7 mfio power-down register .................................................................................................. ..............9-11 10. ir module ................................................................................................................... ..........................................10-1 10.1 overview ................................................................................................................... ...................................10-1 10.1.1 related pins............................................................................................................. ..............................10-1 10.2 consumer ir................................................................................................................ .................................10-2 10.2.1 requirements............................................................................................................. ............................10-2 10.2.2 implementation ........................................................................................................... ..........................10-2 10.2.3 block diagram ............................................................................................................ ..........................10-2 10.2.4 functional description ................................................................................................... .......................10-3 10.2.5 related interrupts ....................................................................................................... ...........................10-3 10.3 two-way communication via ir ............................................................................................... .................10-4 10.3.1 requirements............................................................................................................. ............................10-4 10.3.2 block diagram ............................................................................................................ ..........................10-5 10.4 carrier detect state machine............................................................................................... .........................10-6 10.4.1 requirements............................................................................................................. ............................10-6 10.4.2 block diagram ............................................................................................................ ..........................10-6 10.4.3 functional description ................................................................................................... .......................10-7 10.4.4 related interrupts ....................................................................................................... ...........................10-7 10.5 ir registers ............................................................................................................... ...................................10-8 10.5.1 ir control 1 register .................................................................................................... ........................10-8 10.5.2 ir control 2 register .................................................................................................... ........................10-9 10.5.3 ir holding register ...................................................................................................... ......................10-10 11. magicbus module............................................................................................................. .....................................11-1 11.1 overview ................................................................................................................... ...................................11-1 11.1.1 related pins............................................................................................................. ..............................11-1 11.2 interface requirements..................................................................................................... ............................11-2 11.2.1 timing requirements ...................................................................................................... ......................11-2 11.2.2 data formats ............................................................................................................. ............................11-2 11.2.3 command words............................................................................................................ .......................11-3 11.3 implementation............................................................................................................. ................................11-4 www.datasheet.in table of contents v 11.3.1 block diagram ............................................................................................................ ..........................11-4 11.3.2 transmitter .............................................................................................................. ..............................11-5 11.3.3 receiver................................................................................................................. ................................11-6 11.3.4 control logic ............................................................................................................ ............................11-7 11.3.5 dma address generation................................................................................................... ..................11-9 11.3.6 related interrupts ....................................................................................................... .........................11-10 11.4 magicbus registers......................................................................................................... ............................11-11 11.4.1 magicbus control 1 register.............................................................................................. .................11-11 11.4.2 magicbus control 2 register.............................................................................................. .................11-13 11.4.3 magicbus dma control 1 register .......................................................................................... ..........11-14 11.4.4 magicbus dma control 2 register .......................................................................................... ..........11-14 11.4.5 magicbus dma count ....................................................................................................... .................11-14 11.4.6 magicbus transmit holding register....................................................................................... ...........11-15 11.4.7 magicbus receive holding register ........................................................................................ ...........11-15 12. power module ................................................................................................................ .......................................12-1 12.1 overview ................................................................................................................... ...................................12-1 12.1.1 system power control overview ............................................................................................ ..............12-1 12.1.2 power state transition diagram........................................................................................... .................12-2 12.1.3 power supply lines in the system......................................................................................... ...............12-3 12.1.4 related pins............................................................................................................. ..............................12-4 12.2 description ................................................................................................................ ...................................12-5 12.2.1 power on reset........................................................................................................... ..........................12-5 12.2.2 the 1 st power up...................................................................................................................... .............12-6 12.2.3 power down............................................................................................................... ...........................12-7 12.2.4 power up................................................................................................................. ..............................12-8 12.2.5 stop cpu................................................................................................................. ..............................12-9 12.2.6 forced shutdown.......................................................................................................... .......................12-10 12.2.7 memory power down ........................................................................................................ .................12-10 12.2.8 stop timer............................................................................................................... ............................12-10 12.2.9 power module interrupts.................................................................................................. ...................12-11 12.3 power registers ............................................................................................................ ..............................12-12 12.3.1 power control register ................................................................................................... ....................12-12 13. sib module .................................................................................................................. .........................................13-1 13.1 overview ................................................................................................................... ...................................13-1 13.1.1 related pins............................................................................................................. ..............................13-2 13.2 block diagram.............................................................................................................. ................................13-3 13.2.1 holding and shift registers .............................................................................................. ....................13-4 13.2.2 clock and sync generation................................................................................................ ...................13-4 13.3 interface requirements..................................................................................................... ............................13-6 13.3.1 frame structure .......................................................................................................... ...........................13-6 13.3.2 timing requirements ...................................................................................................... ......................13-6 13.3.3 configurations........................................................................................................... ............................13-7 13.3.4 sample rates............................................................................................................. ............................13-8 13.3.5 enable/disable sequencing................................................................................................ .................13-10 13.3.6 data formats ............................................................................................................. ..........................13-11 13.3.7 subframe formats ......................................................................................................... ......................13-12 13.4 dma address generation ..................................................................................................... .....................13-15 13.5 related interrupts ......................................................................................................... ..............................13-17 www.datasheet.in table of contents vi 13.6 sib registers .............................................................................................................. ................................13-19 13.6.1 sib size register ........................................................................................................ ........................13-19 13.6.2 sib sound rx start register .............................................................................................. ................13-19 13.6.3 sib sound tx start register .............................................................................................. ................13-20 13.6.4 sib telecom rx start register............................................................................................ ...............13-20 13.6.5 sib telecom tx start register............................................................................................ ...............13-20 13.6.6 sib control register ..................................................................................................... ......................13-21 13.6.7 sib sound tx holding register............................................................................................ .............13-25 13.6.8 sib sound rx holding register............................................................................................ .............13-25 13.6.9 sib telecom tx holding register .......................................................................................... ...........13-25 13.6.10 sib telecom rx holding register ......................................................................................... ............13-26 13.6.11 sib subframe 0 control register......................................................................................... ...............13-26 13.6.12 sib subframe 1 control register......................................................................................... ...............13-26 13.6.13 sib subframe 0 status register .......................................................................................... ................13-27 13.6.14 sib subframe 1 status register .......................................................................................... ................13-27 13.6.15 sib dma control register................................................................................................ .................13-27 14. spi module.................................................................................................................. ..........................................14-1 14.1 overview ................................................................................................................... ...................................14-1 14.1.1 related pins............................................................................................................. ..............................14-1 14.2 description ................................................................................................................ ...................................14-2 14.2.1 block diagram ............................................................................................................ ..........................14-2 14.2.2 baud rate generator ...................................................................................................... .......................14-2 14.2.3 transmitter/receiver ..................................................................................................... ........................14-3 14.2.4 clkpol/phapol............................................................................................................ ...................14-4 14.2.5 inter character delay counter ............................................................................................ ..................14-5 14.2.6 spi interrupts ........................................................................................................... .............................14-5 14.3 spi registers.............................................................................................................. ...................................14-6 14.3.1 spi control register..................................................................................................... .........................14-6 14.3.2 spi transmitter holding register ......................................................................................... ................14-7 14.3.3 spi receiver holding register............................................................................................ ..................14-8 15. timer module................................................................................................................ ........................................15-1 15.1 overview ................................................................................................................... ...................................15-1 15.1.1 related pins............................................................................................................. ..............................15-1 15.2 rtc ........................................................................................................................ ......................................15-2 15.2.1 rtc block diagram........................................................................................................ ......................15-2 15.2.2 rtc description.......................................................................................................... ..........................15-3 15.2.3 rtc interrupts........................................................................................................... ............................15-3 15.3 periodic timer ............................................................................................................. .................................15-4 15.3.1 periodic timer block diagram............................................................................................. .................15-4 15.3.2 periodic timer description ............................................................................................... ....................15-4 15.3.3 periodic timer interrupts ................................................................................................ ......................15-4 15.4 timer registers............................................................................................................ .................................15-5 15.4.1 rtc register............................................................................................................. ............................15-5 15.4.2 alarm register ........................................................................................................... ...........................15-5 15.4.3 timer control register................................................................................................... .......................15-6 15.4.4 periodic timer register.................................................................................................. .......................15-7 16. uart module................................................................................................................. ......................................16-1 16.1 overview ................................................................................................................... ...................................16-1 www.datasheet.in table of contents vii 16.1.1 related pins............................................................................................................. ..............................16-1 16.2 overall operation .......................................................................................................... ...............................16-2 16.2.1 power on/off ............................................................................................................. ...........................16-2 16.2.2 baud rate and communication parameters ................................................................................... .......16-2 16.2.3 interrupt operation...................................................................................................... ..........................16-3 16.2.4 dma operation ............................................................................................................ ........................16-5 16.2.5 internal loopback ........................................................................................................ .........................16-6 16.3 transmitter operation...................................................................................................... .............................16-7 16.3.1 transmitter pulse output operation....................................................................................... ...............16-8 16.3.2 transmitter disable operation ............................................................................................ ..................16-8 16.3.3 transmitter break operation.............................................................................................. ...............16-8 16.3.4 transmitter overrun ...................................................................................................... ........................16-8 16.4 receiver operation ......................................................................................................... ..............................16-9 16.4.1 receiver break operation ................................................................................................. ..............16-10 16.4.2 receiver frame error condition ........................................................................................... ..............16-10 16.4.3 receiver overrun condition ............................................................................................... ................16-10 16.4.4 receiver parity error condition.......................................................................................... ................16-10 16.4.5 receiver pulse operation ................................................................................................. ...................16-10 16.5 uart registers............................................................................................................. .............................16-11 16.5.1 uart control 1 register.................................................................................................. ..................16-11 16.5.2 uart control 2 register.................................................................................................. ..................16-14 16.5.3 uart dma control 1 register .............................................................................................. ...........16-14 16.5.4 uart dma control 2 register .............................................................................................. ...........16-14 16.5.5 uart dma count ........................................................................................................... ..................16-15 16.5.6 uart transmit holding register........................................................................................... ............16-15 16.5.7 uart receiver holding register........................................................................................... ............16-15 17. video module................................................................................................................ ........................................17-1 17.1 overview ................................................................................................................... ...................................17-1 17.1.1 related pins............................................................................................................. ..............................17-1 17.2 interface requirements..................................................................................................... ............................17-2 17.2.1 display types............................................................................................................ ............................17-2 17.2.2 timing requirements ...................................................................................................... ......................17-5 17.3 implementation............................................................................................................. ................................17-8 17.3.1 block diagram ............................................................................................................ ..........................17-8 17.3.2 video state machine ...................................................................................................... .......................17-9 17.3.3 horizontal counter....................................................................................................... .......................17-10 17.3.4 line counter............................................................................................................. ...........................17-11 17.3.5 dma address generation................................................................................................... ................17-11 17.3.6 video fifo............................................................................................................... ...........................17-13 17.3.7 gray scale lut ........................................................................................................... .......................17-14 17.3.8 color lut................................................................................................................ ...........................17-15 17.3.9 dithering ................................................................................................................ .............................17-17 17.3.10 related interrupts ...................................................................................................... ..........................17-18 17.4 video registers............................................................................................................ ...............................17-19 17.4.1 video control 1 register................................................................................................. ....................17-19 17.4.2 video control 2 register................................................................................................. ....................17-21 17.4.3 video control 3 register................................................................................................. ....................17-21 17.4.4 video control 4 register................................................................................................. ....................17-22 www.datasheet.in table of contents viii 17.4.5 video control 5 register................................................................................................. ....................17-23 17.4.6 video control 6 register................................................................................................. ....................17-23 17.4.7 video control 7 register................................................................................................. ....................17-24 17.4.8 video control 8 register................................................................................................. ....................17-24 17.4.9 video control 9 register................................................................................................. ....................17-25 17.4.10 video control 10 register............................................................................................... ....................17-26 17.4.11 video control 11 register ............................................................................................... ....................17-26 17.4.12 video control 12 register............................................................................................... ....................17-27 17.4.13 video control 13 register............................................................................................... ....................17-27 17.4.14 video control 14 register............................................................................................... ....................17-28 18. electrical characteristics .................................................................................................. .....................................18-1 18.1 electrical characteristics of TMPR3911bu/bxb ............................................................................... ........18-1 18.1.1 absolute maximum ratings (TMPR3911bu/bxb) ..............................................................................18 -1 18.1.2 recommended operating conditions (TMPR3911bu/bxb) ................................................................18-1 18.1.3 dc characteristics (TMPR3911bu/bxb) ...................................................................................... ......18-2 18.1.4 crystal oscillator characteristics (TMPR3911bu/bxb)...................................................................... .18-3 18.1.5 TMPR3911bu/bxb timing.................................................................................................... .............18-4 18.1.6 ac characteristics (TMPR3911bu/bxb) ...................................................................................... ......18-5 18.2 electrical characteristics of tmpr3912au-92/xb-92 .......................................................................... ...18-27 18.2.1 absolute maximum ratings (tmpr3912au-92/xb-92) ....................................................................18-27 18.2.2 recommended operating conditions (tmpr3912au-92/xb-92) ......................................................18-27 18.2.3 dc characteristics (tmpr3912au-92/xb-92) ................................................................................. .18-28 18.2.4 crystal oscillator characteristics (tmpr3912au-92/xb-92) ............................................................18-29 18.2.5 definition of ac specification (tmpr3912au-92/xb-92)...............................................................18-30 18.2.6 ac characteristics (tmpr3912au-92/xb-92) ................................................................................. .18-31 19. package dimension ........................................................................................................... ....................................19-1 19.1 TMPR3911bu................................................................................................................. .............................19-1 19.2 tmpr3912au-92 .............................................................................................................. ..........................19-2 19.3 tmpr3912xb-92 .............................................................................................................. ..........................19-3 19.4 TMPR3911bxb ................................................................................................................ ...........................19-4 appendix a differences among TMPR3911/12...................................................................................... ....................a-1 appendix b access timing chart ................................................................................................ ............................... b-1 www.datasheet.in handling precautions www.datasheet.in www.datasheet.in 1 using toshiba semiconductors safely 1-1 1. using toshiba semiconductors safely toshiba are continually working to improve the quality and the reliability of their products. nevertheless, semiconductor devices in general can malfunction or fail due to their inherent electrical sensitivity and vulnerability to physical stress. it is the responsibility of the buyer, when utilizing toshiba products, to observe standards of safety, and to avoid situations in which a malfunction or failure of a toshiba product could cause loss of human life, bodily injury or damage to property. in developing your designs, please ensure that toshiba products are used within specified operating ranges as set forth in the most recent products specifications. also, please keep in mind the precautions and conditions set forth in the toshiba semiconductor reliability handbook. the toshiba products listed in this document are intended for usage in general electronics applications (computer, personal equipment, office equipment, measuring equipment, industrial robotics, domestic appliances, etc.). these toshiba products are neither intended nor warranted for usage in equipment that requires extraordinarily high quality and/or reliability or a malfunction or failure of which may cause loss of human life or bodily injury (?unintended usage?). unintended usage include atomic energy control instruments, airplane or spaceship instruments, transportation instruments, traffic signal instruments, combustion control instruments, medical instruments, all types of safety devices, etc.. unintended usage of toshiba products listed in this document shall be made at the customer?s own risk. www.datasheet.in 1 using toshiba semiconductors safely 1-2 www.datasheet.in 2 safety precautions 2-1 2. safety precautions this section lists important precautions which users of semiconductor devices (and anyone else) should observe in order to avoid injury and damage to property, and to ensure safe and correct use of devices. please be sure that you understand the meanings of the labels and the graphic symbol described below before you move on to the detailed descriptions of the precautions. [explanation of labels] indicates an imminently hazardous situation which will result in death or serious injury if you do not follow instructions. indicates a potentially hazardous situation which could result in death or serious injury if you do not follow instructions. indicates a potentially hazardous situation which if not avoided, may result in minor injury or moderate injury. [explanation of graphic symbol] graphic symbol meaning indicates that caution is required (laser beam is dangerous to eyes). www.datasheet.in 2 safety precautions 2-2 2.1 general precautions regarding semiconductor devices do not use devices under conditions exceeding their absolute maximum ratings (e.g. current, voltage, power dissipation or temperature). this may cause the device to break down, degrade its performance, or cause it to catch fire or explode resulting in injury. do not insert devices in the wrong orientation. make sure that the positive and negative terminals of power supplies are connected correctly. otherwise the rated maximum current or power dissipation may be exceeded and the device may break down or undergo performance degradation, causing it to catch fire or explode and resulting in injury. when power to a device is on, do not touch the device?s heat sink. heat sinks become hot, so you may burn your hand. do not touch the tips of device leads. because some types of device have leads with pointed tips, you may prick your finger. when conducting any kind of evaluation, inspection or testing, be sure to connect the testing equipment?s electrodes or probes to the pins of the device under test before powering it on. otherwise, you may receive an electric shock causing injury. before grounding an item of measuring equipment or a soldering iron, check that there is no electrical leakage from it. electrical leakage may cause the device which you are testing or soldering to break down, or could give you an electric shock. always wear protective glasses when cutting the leads of a device with clippers or a similar tool. if you do not, small bits of metal flying off the cut ends may damage your eyes. www.datasheet.in 2 safety precautions 2-3 2.2 precautions specific to each product group 2.2.1 optical semiconductor devices when a visible semiconductor laser is operating, do not look directly into the laser beam or look through the optical system. this is highly likely to impair vision, and in the worst case may cause blindness. if it is necessary to examine the laser apparatus, for example to inspect its optical characteristics, always wear the appropri ate type of laser protective glasses as stipulated by iec standard iec825-1. ensure that the current flowing in an led device does not exceed the device?s maximum rated current. this is particularly important for resin-packaged led devices, as excessive current may cause the package resin to blow up, scattering resin fragments and causing injury. when testing the dielectric strength of a photocoupler, use testing equipment which can shut off the supply voltage to the photocoupler. if you detect a leakage current of more than 100 2.2.2 power devices never touch a power device while it is powered on. also, after turning off a power device, do not touch it until it has thoroug hly discharged all remaining electrical charge. touching a power device while it is powered on or still charged could cause a severe electric shock, resulting in death or seri ous injury. when conducting any kind of evaluation, inspection or testing, be sure to connect the testing equipment?s electrodes or probes to the device under test before powering it on. when you have finished, discharge any electrical charge remaining in the device. connecting the electrodes or probes of testing equipment to a device while it is powered on may result in electric shock, causi ng injury. www.datasheet.in 2 safety precautions 2-4 do not use devices under conditions which exceed their absolute maximum ratings (current, voltage, power dissipation, temperature etc.). this may cause the device to break down, causing a large short-circuit current to flow, which may in turn cause it to catch fir e or explode, resulting in fire or injury. use a unit which can detect short-circuit currents and which will shut off the power supply if a short-circuit occurs. if the power supply is not shut off, a large short-circuit current will flow continuously, which may in turn cause the device t o catch fire or explode, resulting in fire or injury. when designing a case for enclosing your system, consider how best to protect the user from shrapnel in the event of the device catching fire or exploding. flying shrapnel can cause injury. when conducting any kind of evaluation, inspection or testing, always use protective safety tools such as a cover for the devic e. otherwise you may sustain injury caused by the device catching fire or exploding. make sure that all metal casings in your design are grounded to earth. even in modules where a device?s electrodes and metal casing are insulated, capacitance in the module may cause the electrostatic potential in the casing to rise. dielectric breakdown may cause a high voltage to be applied to the casing, causing electric shock and injury to anyone touching it. when designing the heat radiation and safety features of a system incorporating high-speed rectifiers, remember to take the device?s forward and reverse losses into account. the leakage current in these devices is greater than that in ordinary rectifiers; as a result, if a high-speed rectifier is use d in an extreme environment (e.g. at high temperature or high voltage), its reverse loss may increase, causing thermal runaway to occur . this may in turn cause the device to explode and scatter shrapnel, resulting in injury to the user. a design should ensure that, except when the main circuit of the device is active, reverse bias is applied to the device gate w hile electricity is conducted to control circuits, so that the main circuit will become inactive. malfunction of the device may cause serious accidents or injuries. when conducting any kind of evaluation, inspection or testing, either wear protective gloves or wait until the device has coole d properly before handling it. devices become hot when they are operated. even after the power has been turned off, the device will retain residual heat which may cause a burn to anyone touching it. 2.2.3 bipolar ics (for use in automobiles) if your design includes an inductive load such as a motor coil, incorporate diodes or similar devices into the design to preven t negative current from flowing in. the load current generated by powering the device on and off may cause it to function erratically or to break down, which could in turn cause injury. ensure that the power supply to any device which incorporates protective functions is stable. if the power supply is unstable, the device may operate erratically, preventing the protective functions from working correctly . if protective functions fail, the device may break down causing injury to the user. www.datasheet.in 3 general safety precautions and usage considerations 3-1 3. general safety precautions and usage considerations this section is designed to help you gain a better understanding of semiconductor devices, so as to ensure the safety, quality and reliability of the devices which you incorporate into your designs. 3.1 from incoming to shipping 3.1.1 electrostatic discharge (esd) when handling individual devices (which are not yet mounted on a printed circuit board), be sure that the environment is protected against electrostatic electricity. operators should wear anti-static clothing, and containers and other objects which come into direct contact with devices should be made of anti-static materials and should be grounded to earth via an 0.5- to 1.0-m ? protective resistor. please follow the precautions described below; this is particularly important for devices which are marked ?be careful of static.?. (1) work environment ? when humidity in the working environment decreases, the human body and other insulators can easily become charged with static electricity due to friction. maintain the recommended humidity of 40% to 60% in the work environment, while also taking into account the fact that moisture-proof-packed products may absorb moisture after unpacking. ? be sure that all equipment, jigs and tools in the working area are grounded to earth. ? place a conductive mat over the floor of the work area, or take other appropriate measures, so that the floor surface is protected against static electricity and is grounded to earth. the surface resistivity should be 10 4 to 10 8 ? /sq and the resistance between surface and ground, 7.5 10 5 to 10 8 ? ? cover the workbench surface also with a conductive mat (with a surface resistivity of 10 4 to 10 8 ? /sq, for a resistance between surface and ground of 7.5 10 5 to 10 8 ? ) . the purpose of this is to disperse static electricity on the surface (through resistive components) and ground it to earth. workbench surfaces must not be constructed of low-resistance metallic materials that allow rapid static discharge when a charged device touches them directly. ? pay attention to the following points when using automatic equipment in your workplace: (a) when picking up ics with a vacuum unit, use a conductive rubber fitting on the end of the pick-up wand to protect against electrostatic charge. (b) minimize friction on ic package surfaces. if some rubbing is unavoidable due to the device?s mechanical structure, minimize the friction plane or use material with a small friction coefficient and low electrical resistance. also, consider the use of an ionizer. (c) in sections which come into contact with device lead terminals, use a material which dissipates static electricity. (d) ensure that no statically charged bodies (such as work clothes or the human body) touch the devices. www.datasheet.in 3 general safety precautions and usage considerations 3-2 (e) make sure that sections of the tape carrier which come into contact with installation devices or other electrical machinery are made of a low-resistance material. (f) make sure that jigs and tools used in the assembly process do not touch devices. (g) in processes in which packages may retain an electrostatic charge, use an ionizer to neutralize the ions. ? make sure that crt displays in the working area are protected against static charge, for example by a vdt filter. as much as possible, avoid turning displays on and off. doing so can cause electrostatic induction in devices. ? keep track of charged potential in the working area by taking periodic measurements. ? ensure that work chairs are protected by an anti-static textile cover and are grounded to the floor surface by a grounding chain. (suggested resistance between the seat surface and grounding chain is 7.5 10 5 to 10 12 ? .) ? install anti-static mats on storage shelf surfaces. (suggested surface resistivity is 10 4 to 10 8 ? /sq; suggested resistance between surface and ground is 7.5 10 5 to 10 8 ? .) ? for transport and temporary storage of devices, use containers (boxes, jigs or bags) that are made of anti-static materials or materials which dissipate electrostatic charge. ? make sure that cart surfaces which come into contact with device packaging are made of materials which will conduct static electricity, and verify that they are grounded to the floor surface via a grounding chain. ? in any location where the level of static electricity is to be closely controlled, the ground resistance level should be class 3 or above. use different ground wires for all items of equipment which may come into physical contact with devices. (2) operating environment ? operators must wear anti-static clothing and conductive shoes (or a leg or heel strap). ? operators must wear a wrist strap grounded to earth via a resistor of about 1 m ? . ? soldering irons must be grounded from iron tip to earth, and must be used only at low voltages (6 v to 24 v). ? if the tweezers you use are likely to touch the device terminals, use anti-static tweezers and in particular avoid metallic tweezers. if a charged device touches a low-resistance tool, rapid discharge can occur. when using vacuum tweezers, attach a conductive chucking pat to the tip, and connect it to a dedicated ground used especially for anti-static purposes (suggested resistance value: 10 4 to 10 8 ? ). ? do not place devices or their containers near sources of strong electrical fields (such as above a crt). www.datasheet.in 3 general safety precautions and usage considerations 3-3 ? when storing printed circuit boards which have devices mounted on them, use a board container or bag that is protected against static charge. to avoid the occurrence of static charge or discharge due to friction, keep the boards separate from one other and do not stack them directly on top of one another. ? ensure, if possible, that any articles (such as clipboards) which are brought to any location where the level of static electricity must be closely controlled are constructed of anti-static materials. ? in cases where the human body comes into direct contact with a device, be sure to wear anti- static finger covers or gloves (suggested resistance value: 10 8 ? or less). ? equipment safety covers installed near devices should have resistance ratings of 10 9 ? or less. ? if a wrist strap cannot be used for some reason, and there is a possibility of imparting friction to devices, use an ionizer. ? the transport film used in tcp products is manufactured from materials in which static charges tend to build up. when using these products, install an ionizer to prevent the film from being charged with static electricity. also, ensure that no static electricity will be applied to the product?s copper foils by taking measures to prevent static occuring in the peripheral equipment. 3.1.2 vibration, impact and stress handle devices and packaging materials with care. to avoid damage to devices, do not toss or drop packages. ensure that devices are not subjected to mechanical vibration or shock during transportation. ceramic package devices and devices in canister-type packages which have empty space inside them are subject to damage from vibration and shock because the bonding wires are secured only at their ends. plastic molded devices, on the other hand, have a relatively high level of resistance to vibration and mechanical shock because their bonding wires are enveloped and fixed in resin. however, when any device or package type is installed in target equipment, it is to some extent susceptible to wiring disconnections and other damage from vibration, shock and stressed solder junctions. therefore when devices are incorporated into the design of equipment which will be subject to vibration, the structural design of the equipment must be thought out carefully. if a device is subjected to especially strong vibration, mechanical shock or stress, the package or the chip itself may crack. in products such as ccds which incorporate window glass, this could cause surface flaws in the glass or cause the connection between the glass and the ceramic to separate. furthermore, it is known that stress applied to a semiconductor device through the package changes the resistance characteristics of the chip because of piezoelectric effects. in analog circuit design attention must be paid to the problem of package stress as well as to the dangers of vibration and shock as described above. vibration www.datasheet.in 3 general safety precautions and usage considerations 3-4 3.2 storage 3.2.1 general storage ? avoid storage locations where devices will be exposed to moisture or direct sunlight. ? follow the instructions printed on the device cartons regarding transportation and storage. ? the storage area temperature should be kept within a temperature range of 5c to 35c, and relative humidity should be maintained at between 45% and 75%. ? do not store devices in the presence of harmful (especially corrosive) gases, or in dusty conditions. ? use storage areas where there is minimal temperature fluctuation. rapid temperature changes can cause moisture to form on stored devices, resulting in lead oxidation or corrosion. as a result, the solderability of the leads will be degraded. ? when repacking devices, use anti-static containers. ? do not allow external forces or loads to be applied to devices while they are in storage. ? if devices have been stored for more than two years, their electrical characteristics should be tested and their leads should be tested for ease of soldering before they are used. 3.2.2 moisture-proof packing moisture-proof packing should be handled with care. the handling procedure specified for each packing type should be followed scrupulously. if the proper procedures are not followed, the quality and reliability of devices may be degraded. this section describes general precautions for handling moisture-proof packing. since the details may differ from device to device, refer also to the relevant individual datasheets or databook. (1) general precautions follow the instructions printed on the device cartons regarding transportation and storage. ? do not drop or toss device packing. the laminated aluminum material in it can be rendered ineffective by rough handling. ? the storage area temperature should be kept within a temperature range of 5c to 30c, and relative humidity should be maintained at 90% (max). use devices within 12 months of the date marked on the package seal. humidity: temperature: www.datasheet.in 3 general safety precautions and usage considerations 3-5 ? if the 12-month storage period has expired, or if the 30% humidity indicator shown in figure 1 is pink when the packing is opened, it may be advisable, depending on the device and packing type, to back the devices at high temperature to remove any moisture. please refer to the table below. after the pack has been opened, use the devices in a 5 c to 30 c. 60% rh environment and within the effective usage period listed on the moisture-proof package. if the effective usage period has expired, or if the packing has been stored in a high-humidity environment, bake the devices at high temperature. packing moisture removal tray if the packing bears the ?heatproof? marking or indicates the maximum temperature which it can withstand, bake at 125 ? when baking devices, protect the devices from static electricity. ? moisture indicators can detect the approximate humidity level at a standard temperature of 25 c. 6-point indicators and 3-point indicators are currently in use, but eventually all indicators will be 3-point indicators. danger if pink change desiccant read at lavender between pink & blue 10% 20% 30% 40% 50% 60% humidity indicator danger if pink read at lavender between pink & blue 20 30 40 humidity indicator (a) 6-point indicator (b) 3-point indicator figure 1 humidity indicator www.datasheet.in 3 general safety precautions and usage considerations 3-6 3.3 design care must be exercised in the design of electronic equipment to achieve the desired reliability. it is important not only to adhere to specifications concerning absolute maximum ratings and recommended operating conditions, it is also important to consider the overall environment in which equipment will be used, including factors such as the ambient temperature, transient noise and voltage and current surges, as well as mounting conditions which affect device reliability. this section describes some general precautions which you should observe when designing circuits and when mounting devices on printed circuit boards. for more detailed information about each product family, refer to the relevant individual technical datasheets available from toshiba. 3.3.1 absolute maximum ratings do not use devices under conditions in which their absolute maximum ratings (e.g. current, voltage, power dissipation or temperature) will be exceeded. a device may break down or its performance may be degraded, causing it to catch fire or explode resulting in injury to the user. the absolute maximum ratings are rated values which must not be exceeded during operation, even for an instant. although absolute maximum ratings differ from product to product, they essentially concern the voltage and current at each pin, the allowable power dissipation, and the junction and storage temperatures. if the voltage or current on any pin exceeds the absolute maximum rating, the device?s internal circuitry can become degraded. in the worst case, heat generated in internal circuitry can fuse wiring or cause the semiconductor chip to break down. if storage or operating temperatures exceed rated values, the package seal can deteriorate or the wires can become disconnected due to the differences between the thermal expansion coefficients of the materials from which the device is constructed. 3.3.2 recommended operating conditions the recommended operating conditions for each device are those necessary to guarantee that the device will operate as specified in the datasheet. if greater reliability is required, derate the device?s absolute maximum ratings for voltage, current, power and temperature before using it. 3.3.3 derating when incorporating a device into your design, reduce its rated absolute maximum voltage, current, power dissipation and operating temperature in order to ensure high reliability. since derating differs from application to application, refer to the technical datasheets available for the various devices used in your design. 3.3.4 unused pins if unused pins are left open, some devices can exhibit input instability problems, resulting in malfunctions such as abrupt increase in current flow. similarly, if the unused output pins on a device are connected to the power supply pin, the ground pin or to other output pins, the ic may malfunction or break down. since the details regarding the handling of unused pins differ from device to device and from pin www.datasheet.in 3 general safety precautions and usage considerations 3-7 to pin, please follow the instructions given in the relevant individual datasheets or databook. cmos logic ic inputs, for example, have extremely high impedance. if an input pin is left open, it can easily pick up extraneous noise and become unstable. in this case, if the input voltage level reaches an intermediate level, it is possible that both the p-channel and n-channel transistors will be turned on, allowing unwanted supply current to flow. therefore, ensure that the unused input pins of a device are connected to the power supply (vcc) pin or ground (gnd) pin of the same device. for details of what to do with the pins of heat sinks, refer to the relevant technical datasheet and databook. 3.3.5 latch-up latch-up is an abnormal condition inherent in cmos devices, in which vcc gets shorted to ground. this happens when a parasitic pn-pn junction (thyristor structure) internal to the cmos chip is turned on, causing a large current of the order of several hundred ma or more to flow between vcc and gnd, eventually causing the device to break down. latch-up occurs when the input or output voltage exceeds the rated value, causing a large current to flow in the internal chip, or when the voltage on the vcc (vdd) pin exceeds its rated value, forcing the internal chip into a breakdown condition. once the chip falls into the latch-up state, even though the excess voltage may have been applied only for an instant, the large current continues to flow between vcc (vdd) and gnd (vss). this causes the device to heat up and, in extreme cases, to emit gas fumes as well. to avoid this problem, observe the following precautions: (1) do not allow voltage levels on the input and output pins either to rise above vcc (vdd) or to fall below gnd (vss). also, follow any prescribed power-on sequence, so that power is applied gradually or in steps rather than abruptly. (2) do not allow any abnormal noise signals to be applied to the device. (3) set the voltage levels of unused input pins to vcc (vdd) or gnd (vss). (4) do not connect output pins to one another. 3.3.6 input/output protection wired-and configurations, in which outputs are connected together, cannot be used, since this short-circuits the outputs. outputs should, of course, never be connected to vcc (vdd) or gnd (vss). furthermore, ics with tri-state outputs can undergo performance degradation if a shorted output current is allowed to flow for an extended period of time. therefore, when designing circuits, make sure that tri-state outputs will not be enabled simultaneously. 3.3.7 load capacitance some devices display increased delay times if the load capacitance is large. also, large charging and discharging currents will flow in the device, causing noise. furthermore, since outputs are shorted for a relatively long time, wiring can become fused. consult the technical information for the device being used to determine the recommended load capacitance. www.datasheet.in 3 general safety precautions and usage considerations 3-8 3.3.8 thermal design the failure rate of semiconductor devices is greatly increased as operating temperatures increase. as shown in figure 2, the internal thermal stress on a device is the sum of the ambient temperature and the temperature rise due to power dissipation in the device. therefore, to achieve optimum reliability, observe the following precautions concerning thermal design: (1) keep the ambient temperature (ta) as low as possible. (2) if the device?s dynamic power dissipation is relatively large, select the most appropriate circuit board material, and consider the use of heat sinks or of forced air cooling. such measures will help lower the thermal resistance of the package. (3) derate the device?s absolute maximum ratings to minimize thermal stress from power dissipation. ja = jc + ca ja = (tj?ta) / p jc = (tj?tc) / p ca = (tc?ta) / p in which ja = thermal resistance between junction and surrounding air (c/w) jc = thermal resistance between junction and package surface, or internal thermal resistance (c/w) ca = thermal resistance between package surface and surrounding air, or external thermal resistance (c/w) tj = junction temperature or chip temperature (c) tc = package surface temperature or case temperature (c) ta = ambient temperature (c) p = power dissipation (w) tc figure 2 thermal resistance of package 3.3.9 interfacing when connecting inputs and outputs between devices, make sure input voltage (v il /v ih ) and output voltage (v ol /v oh ) levels are matched. otherwise, the devices may malfunction. when connecting devices operating at different supply voltages, such as in a dual-power-supply system, be aware that erroneous power-on and power-off sequences can result in device breakdown. for details of how to interface particular devices, consult the relevant technical datasheets and databooks. if you have any questions or doubts about interfacing, contact your nearest toshiba office or distributor. www.datasheet.in 3 general safety precautions and usage considerations 3-9 3.3.10 decoupling spike currents generated during switching can cause vcc (vdd) and gnd (vss) voltage levels to fluctuate, causing ringing in the output waveform or a delay in response speed. (the power supply and gnd wiring impedance is normally 50 ? to 100 ? .) for this reason, the impedance of power supply lines with respect to high frequencies must be kept low. this can be accomplished by using thick and short wiring for the vcc (vdd) and gnd (vss) lines and by installing decoupling capacitors (of approximately 0.01 f to 1 f capacitance) as high-frequency filters between vcc (vdd) and gnd (vss) at strategic locations on the printed circuit board. for low-frequency filtering, it is a good idea to install a 10- to 100- f capacitor on the printed circuit board (one capacitor will suffice). if the capacitance is excessively large, however, (e.g. several thousand f) latch-up can be a problem. be sure to choose an appropriate capacitance value. an important point about wiring is that, in the case of high-speed logic ics, noise is caused mainly by reflection and crosstalk, or by the power supply impedance. reflections cause increased signal delay, ringing, overshoot and undershoot, thereby reducing the device?s safety margins with respect to noise. to prevent reflections, reduce the wiring length by increasing the device mounting density so as to lower the inductance (l) and capacitance (c) in the wiring. extreme care must be taken, however, when taking this corrective measure, since it tends to cause crosstalk between the wires. in practice, there must be a trade-off between these two factors. 3.3.11 external noise printed circuit boards with long i/o or signal pattern lines are vulnerable to induced noise or surges from outside sources. consequently, malfunctions or breakdowns can result from overcurrent or overvoltage, depending on the types of device used. to protect against noise, lower the impedance of the pattern line or insert a noise-canceling circuit. protective measures must also be taken against surges. for details of the appropriate protective measures for a particular device, consult the relevant databook. 3.3.12 electromagnetic interference widespread use of electrical and electronic equipment in recent years has brought with it radio and tv reception problems due to electromagnetic interference. to use the radio spectrum effectively and to maintain radio communications quality, each country has formulated regulations limiting the amount of electromagnetic interference which can be generated by individual products. electromagnetic interference includes conduction noise propagated through power supply and telephone lines, and noise from direct electromagnetic waves radiated by equipment. different measurement methods and corrective measures are used to assess and counteract each specific type of noise. difficulties in controlling electromagnetic interference derive from the fact that there is no method available which allows designers to calculate, at the design stage, the strength of the electromagnetic waves which will emanate from each component in a piece of equipment. for this reason, it is only after the prototype equipment has been completed that the designer can take measurements using a dedicated instrument to determine the strength of electromagnetic interference waves. yet it is possible during system design to incorporate some measures for the input/output signals www.datasheet.in 3 general safety precautions and usage considerations 3-10 prevention of electromagnetic interference, which can facilitate taking corrective measures once the design has been completed. these include installing shields and noise filters, and increasing the thickness of the power supply wiring patterns on the printed circuit board. one effective method, for example, is to devise several shielding options during design, and then select the most suitable shielding method based on the results of measurements taken after the prototype has been completed. 3.3.13 peripheral circuits in most cases semiconductor devices are used with peripheral circuits and components. the input and output signal voltages and currents in these circuits must be chosen to match the semiconductor device?s specifications. the following factors must be taken into account. (1) inappropriate voltages or currents applied to a device?s input pins may cause it to operate erratically. some devices contain pull-up or pull-down resistors. when designing your system, remember to take the effect of this on the voltage and current levels into account. (2) the output pins on a device have a predetermined external circuit drive capability. if this drive capability is greater than that required, either incorporate a compensating circuit into your design or carefully select suitable components for use in external circuits. 3.3.14 safety standards each country has safety standards which must be observed. these safety standards include requirements for quality assurance systems and design of device insulation. such requirements must be fully taken into account to ensure that your design conforms to the applicable safety standards. 3.3.15 other precautions (1) when designing a system, be sure to incorporate fail-safe and other appropriate measures according to the intended purpose of your system. also, be sure to debug your system under actual board-mounted conditions. (2) if a plastic-package device is placed in a strong electric field, surface leakage may occur due to the charge-up phenomenon, resulting in device malfunction. in such cases take appropriate measures to prevent this problem, for example by protecting the package surface with a conductive shield. (3) with some microcomputers and mos memory devices, caution is required when powering on or resetting the device. to ensure that your design does not violate device specifications, consult the relevant databook for each constituent device. (4) ensure that no conductive material or object (such as a metal pin) can drop onto and short the leads of a device mounted on a printed circuit board. 3.4 inspection, testing and evaluation 3.4.1 grounding ground all measuring instruments, jigs, tools and soldering irons to earth. electrical leakage may cause a device to break down or may result in electric shock. www.datasheet.in 3 general safety precautions and usage considerations 3-11 3.4.2 inspection sequence c do not insert devices in the wrong orientation. make sure that the positive and negative electrodes of the power supply are correctly connected. otherwise, the rated maximum current or maximum power dissipation may be exceeded and the device may break down or undergo performance degradation, causing it to catch fire or explode, resulting in injury to the user. d when conducting any kind of evaluation, inspection or testing using ac power with a peak voltage of 42.4 v or dc power exceeding 60 v, be sure to connect the electrodes or probes of the testing equipment to the device under test before powering it on. connecting the electrodes or probes of testing equipment to a device while it is powered on may result in electric shock, causing injury. (1) apply voltage to the test jig only after inserting the device securely into it. when applying or removing power, observe the relevant precautions, if any. (2) make sure that the voltage applied to the device is off before removing the device from the test jig. otherwise, the device may undergo performance degradation or be destroyed. (3) make sure that no surge voltages from the measuring equipment are applied to the device. (4) the chips housed in tape carrier packages (tcps) are bare chips and are therefore exposed. during inspection take care not to crack the chip or cause any flaws in it. electrical contact may also cause a chip to become faulty. therefore make sure that nothing comes into electrical contact with the chip. 3.5 mounting there are essentially two main types of semiconductor device package: lead insertion and surface mount. during mounting on printed circuit boards, devices can become contaminated by flux or damaged by thermal stress from the soldering process. with surface-mount devices in particular, the most significant problem is thermal stress from solder reflow, when the entire package is subjected to heat. this section describes a recommended temperature profile for each mounting method, as well as general precautions which you should take when mounting devices on printed circuit boards. note, however, that even for devices with the same package type, the appropriate mounting method varies according to the size of the chip and the size and shape of the lead frame. therefore, please consult the relevant technical datasheet and databook. 3.5.1 lead forming c always wear protective glasses when cutting the leads of a device with clippers or a similar tool. if you do not, small bits of metal flying off the cut ends may damage your eyes. d do not touch the tips of device leads. because some types of device have leads with pointed tips, you may prick your finger. semiconductor devices must undergo a process in which the leads are cut and formed before the devices can be mounted on a printed circuit board. if undue stress is applied to the interior of a device during this process, mechanical breakdown or performance degradation can result. this is attributable primarily to differences between the stress on the device?s external leads and the stress on the internal leads. if the relative difference is great enough, the device?s internal leads, adhesive properties or sealant can be damaged. observe these precautions during the lead- forming process (this does not apply to surface-mount devices): www.datasheet.in 3 general safety precautions and usage considerations 3-12 (1) lead insertion hole intervals on the printed circuit board should match the lead pitch of the device precisely. (2) if lead insertion hole intervals on the printed circuit board do not precisely match the lead pitch of the device, do not attempt to forcibly insert devices by pressing on them or by pulling on their leads. (3) for the minimum clearance specification between a device and a printed circuit board, refer to the relevant device?s datasheet and databook. if necessary, achieve the required clearance by forming the device?s leads appropriately. do not use the spacers which are used to raise devices above the surface of the printed circuit board during soldering to achieve clearance. these spacers normally continue to expand due to heat, even after the solder has begun to solidify; this applies severe stress to the device. (4) observe the following precautions when forming the leads of a device prior to mounting. ? use a tool or jig to secure the lead at its base (where the lead meets the device package) while bending so as to avoid mechanical stress to the device. also avoid bending or stretching device leads repeatedly. ? be careful not to damage the lead during lead forming. ? follow any other precautions described in the individual datasheets and databooks for each device and package type. 3.5.2 socket mounting (1) when socket mounting devices on a printed circuit board, use sockets which match the inserted device?s package. (2) use sockets whose contacts have the appropriate contact pressure. if the contact pressure is insufficient, the socket may not make a perfect contact when the device is repeatedly inserted and removed; if the pressure is excessively high, the device leads may be bent or damaged when they are inserted into or removed from the socket. (3) when soldering sockets to the printed circuit board, use sockets whose construction prevents flux from penetrating into the contacts or which allows flux to be completely cleaned off. (4) make sure the coating agent applied to the printed circuit board for moisture-proofing purposes does not stick to the socket contacts. (5) if the device leads are severely bent by a socket as it is inserted or removed and you wish to repair the leads so as to continue using the device, make sure that this lead correction is only performed once. do not use devices whose leads have been corrected more than once. (6) if the printed circuit board with the devices mounted on it will be subjected to vibration from external sources, use sockets which have a strong contact pressure so as to prevent the sockets and devices from vibrating relative to one another. 3.5.3 soldering temperature profile the soldering temperature and heating time vary from device to device. therefore, when specifying the mounting conditions, refer to the individual datasheets and databooks for the devices used. www.datasheet.in 3 general safety precautions and usage considerations 3-13 (1) using a soldering iron complete soldering within ten seconds for lead temperatures of up to 260c, or within three seconds for lead temperatures of up to 350c. (2) using medium infrared ray reflow ? heating top and bottom with long or medium infrared rays is recommended (see figure 3). long infrared ray heater (preheating) medium infrared ray heater (reflow) product flow figure 3 heating top and bottom with long or medium infrared rays ? complete the infrared ray reflow process within 30 seconds at a package surface temperature of between 210c and 240c. ? refer to figure 4 for an example of a good temperature profile for infrared or hot air reflow. 210 30 s or less time (s) 60-120 s (c) 240 160 140 package surface temperature figure 4 sample temperature profile for infrared or hot air reflow (3) using hot air reflow ? complete hot air reflow within 30 seconds at a package surface temperature of between 210c and 240c. ? for an example of a recommended temperature profile, refer to figure 4 above. (4) using solder flow ? apply preheating for 60 to 120 seconds at a temperature of 150c. ? for lead insertion-type packages, complete solder flow within 10 seconds with the temperature at the stopper (or, if there is no stopper, at a location more than 1.5 mm from the body) which does not exceed 260c. ? for surface-mount packages, complete soldering within 5 seconds at a temperature of 250c or www.datasheet.in 3 general safety precautions and usage considerations 3-14 less in order to prevent thermal stress in the device. ? figure 5 shows an example of a recommended temperature profile for surface-mount packages using solder flow. 5 s or less 60-120 s (c) 250 160 140 package surface temperature time (s) figure 5 sample temperature profile for solder flow 3.5.4 flux cleaning and ultrasonic cleaning (1) when cleaning circuit boards to remove flux, make sure that no residual reactive ions such as na or cl remain. note that organic solvents react with water to generate hydrogen chloride and other corrosive gases which can degrade device performance. (2) washing devices with water will not cause any problems. however, make sure that no reactive ions such as sodium and chlorine are left as a residue. also, be sure to dry devices sufficiently after washing. (3) do not rub device markings with a brush or with your hand during cleaning or while the devices are still wet from the cleaning agent. doing so can rub off the markings. (4) the dip cleaning, shower cleaning and steam cleaning processes all involve the chemical action of a solvent. use only recommended solvents for these cleaning methods. when immersing devices in a solvent or steam bath, make sure that the temperature of the liquid is 50c or below, and that the circuit board is removed from the bath within one minute. (5) ultrasonic cleaning should not be used with hermetically-sealed ceramic packages such as a leadless chip carrier (lcc), pin grid array (pga) or charge-coupled device (ccd), because the bonding wires can become disconnected due to resonance during the cleaning process. even if a device package allows ultrasonic cleaning, limit the duration of ultrasonic cleaning to as short a time as possible, since long hours of ultrasonic cleaning degrade the adhesion between the mold resin and the frame material. the following ultrasonic cleaning conditions are recommended: frequency: 27 khz 29 khz ultrasonic output power: 300 w or less (0.25 w/cm 2 or less) cleaning time: 30 seconds or less suspend the circuit board in the solvent bath during ultrasonic cleaning in such a way that the ultrasonic vibrator does not come into direct contact with the circuit board or the device. www.datasheet.in 3 general safety precautions and usage considerations 3-15 3.5.5 no cleaning if analog devices or high-speed devices are used without being cleaned, flux residues may cause minute amounts of leakage between pins. similarly, dew condensation, which occurs in environments containing residual chlorine when power to the device is on, may cause between- lead leakage or migration. therefore, toshiba recommends that these devices be cleaned. however, if the flux used contains only a small amount of halogen (0.05w% or less), the devices may be used without cleaning without any problems. 3.5.6 mounting tape carrier packages (tcps) (1) when tape carrier packages (tcps) are mounted, measures must be taken to prevent electrostatic breakdown of the devices. (2) if devices are being picked up from tape, or outer lead bonding (olb) mounting is being carried out, consult the manufacturer of the insertion machine which is being used, in order to establish the optimum mounting conditions in advance and to avoid any possible hazards. (3) the base film, which is made of polyimide, is hard and thin. be careful not to cut or scratch your hands or any objects while handling the tape. (4) when punching tape, try not to scatter broken pieces of tape too much. (5) treat the extra film, reels and spacers left after punching as industrial waste, taking care not to destroy or pollute the environment. (6) chips housed in tape carrier packages (tcps) are bare chips and therefore have their reverse side exposed. to ensure that the chip will not be cracked during mounting, ensure that no mechanical shock is applied to the reverse side of the chip. electrical contact may also cause a chip to fail. therefore, when mounting devices, make sure that nothing comes into electrical contact with the reverse side of the chip. if your design requires connecting the reverse side of the chip to the circuit board, please consult toshiba or a toshiba distributor beforehand. 3.5.7 mounting chips devices delivered in chip form tend to degrade or break under external forces much more easily than plastic-packaged devices. therefore, caution is required when handling this type of device. (1) mount devices in a properly prepared environment so that chip surfaces will not be exposed to polluted ambient air or other polluted substances. (2) when handling chips, be careful not to expose them to static electricity. in particular, measures must be taken to prevent static damage during the mounting of chips. with this in mind, toshiba recommend mounting all peripheral parts first and then mounting chips last (after all other components have been mounted). (3) make sure that pcbs (or any other kind of circuit board) on which chips are being mounted do not have any chemical residues on them (such as the chemicals which were used for etching the pcbs). (4) when mounting chips on a board, use the method of assembly that is most suitable for maintaining the appropriate electrical, thermal and mechanical properties of the semiconductor devices used. * for details of devices in chip form, refer to the relevant device?s individual datasheets. www.datasheet.in 3 general safety precautions and usage considerations 3-16 3.5.8 circuit board coating when devices are to be used in equipment requiring a high degree of reliability or in extreme environments (where moisture, corrosive gas or dust is present), circuit boards may be coated for protection. however, before doing so, you must carefully consider the possible stress and contamination effects that may result and then choose the coating resin which results in the minimum level of stress to the device. 3.5.9 heat sinks (1) when attaching a heat sink to a device, be careful not to apply excessive force to the device in the process. (2) when attaching a device to a heat sink by fixing it at two or more locations, evenly tighten all the screws in stages (i.e. do not fully tighten one screw while the rest are still only loosely tightened). finally, fully tighten all the screws up to the specified torque. (3) drill holes for screws in the heat sink exactly as specified. smooth the surface by removing burrs and protrusions or indentations which might interfere with the installation of any part of the device. (4) a coating of silicone compound can be applied between the heat sink and the device to improve heat conductivity. be sure to apply the coating thinly and evenly; do not use too much. also, be sure to use a non-volatile compound, as volatile compounds can crack after a time, causing the heat radiation properties of the heat sink to deteriorate. (5) if the device is housed in a plastic package, use caution when selecting the type of silicone compound to be applied between the heat sink and the device. with some types, the base oil separates and penetrates the plastic package, significantly reducing the useful life of the device. two recommended silicone compounds in which base oil separation is not a problem are yg6260 from toshiba silicone. (6) heat-sink-equipped devices can become very hot during operation. do not touch them, or you may sustain a burn. 3.5.10 tightening torque (1) make sure the screws are tightened with fastening torques not exceeding the torque values stipulated in individual datasheets and databooks for the devices used. (2) do not allow a power screwdriver (electrical or air-driven) to touch devices. 3.5.11 repeated device mounting and usage do not remount or re-use devices which fall into the categories listed below; these devices may cause significant problems relating to performance and reliability. (1) devices which have been removed from the board after soldering (2) devices which have been inserted in the wrong orientation or which have had reverse current applied (3) devices which have undergone lead forming more than once www.datasheet.in 3 general safety precautions and usage considerations 3-17 3.6 protecting devices in the field 3.6.1 temperature semiconductor devices are generally more sensitive to temperature than are other electronic components. the various electrical characteristics of a semiconductor device are dependent on the ambient temperature at which the device is used. it is therefore necessary to understand the temperature characteristics of a device and to incorporate device derating into circuit design. note also that if a device is used above its maximum temperature rating, device deterioration is more rapid and it will reach the end of its usable life sooner than expected. 3.6.2 humidity resin-molded devices are sometimes improperly sealed. when these devices are used for an extended period of time in a high-humidity environment, moisture can penetrate into the device and cause chip degradation or malfunction. furthermore, when devices are mounted on a regular printed circuit board, the impedance between wiring components can decrease under high- humidity conditions. in systems which require a high signal-source impedance, circuit board leakage or leakage between device lead pins can cause malfunctions. the application of a moisture-proof treatment to the device surface should be considered in this case. on the other hand, operation under low-humidity conditions can damage a device due to the occurrence of electrostatic discharge. unless damp-proofing measures have been specifically taken, use devices only in environments with appropriate ambient moisture levels (i.e. within a relative humidity range of 40% to 60%). 3.6.3 corrosive gases corrosive gases can cause chemical reactions in devices, degrading device characteristics. for example, sulphur-bearing corrosive gases emanating from rubber placed near a device (accompanied by condensation under high-humidity conditions) can corrode a device?s leads. the resulting chemical reaction between leads forms foreign particles which can cause electrical leakage. 3.6.4 radioactive and cosmic rays most industrial and consumer semiconductor devices are not designed with protection against radioactive and cosmic rays. devices used in aerospace equipment or in radioactive environments must therefore be shielded. 3.6.5 strong electrical and magnetic fields devices exposed to strong magnetic fields can undergo a polarization phenomenon in their plastic material, or within the chip, which gives rise to abnormal symptoms such as impedance changes or increased leakage current. failures have been reported in lsis mounted near malfunctioning deflection yokes in tv sets. in such cases the device?s installation location must be changed or the device must be shielded against the electrical or magnetic field. shielding against magnetism is especially necessary for devices used in an alternating magnetic field because of the electromotive forces generated in this type of environment. www.datasheet.in 3 general safety precautions and usage considerations 3-18 3.6.6 interference from light (ultraviolet rays, sunlight, fluorescent lamps and incandescent lamps) light striking a semiconductor device generates electromotive force due to photoelectric effects. in some cases the device can malfunction. this is especially true for devices in which the internal chip is exposed. when designing circuits, make sure that devices are protected against incident light from external sources. this problem is not limited to optical semiconductors and eproms. all types of device can be affected by light. 3.6.7 dust and oil just like corrosive gases, dust and oil can cause chemical reactions in devices, which will adversely affect a device?s electrical characteristics. to avoid this problem, do not use devices in dusty or oily environments. this is especially important for optical devices because dust and oil can affect a device?s optical characteristics as well as its physical integrity and the electrical performance factors mentioned above. 3.6.8 fire semiconductor devices are combustible; they can emit smoke and catch fire if heated sufficiently. when this happens, some devices may generate poisonous gases. devices should therefore never be used in close proximity to an open flame or a heat-generating body, or near flammable or combustible materials. 3.7 disposal of devices and packing materials when discarding unused devices and packing materials, follow all procedures specified by local regulations in order to protect the environment against contamination. www.datasheet.in 4 precautions and usage considerations 4-1 4. precautions and usage considerations this section describes matters specific to each product group which need to be taken into consideration when using devices. if the same item is described in sections 3 and 4, the description in section 4 takes precedence. 4.1 microcontrollers 4.1.1 design (1) using resonators which are not specifically recommended for use resonators recommended for use with toshiba products in microcontroller oscillator applications are listed in toshiba databooks along with information about oscillation conditions. if you use a resonator not included in this list, please consult toshiba or the resonator manufacturer concerning the suitability of the device for your application. (2) undefined functions in some microcontrollers certain instruction code values do not constitute valid processor instructions. also, it is possible that the values of bits in registers will become undefined. take care in your applications not to use invalid instructions or to let register bit values become undefined. www.datasheet.in 4 precautions and usage considerations 4-2 www.datasheet.in TMPR3911/3912 www.datasheet.in www.datasheet.in chapter 1 TMPR3911/12 overview 1-1 1. TMPR3911/12 overview 1.1 overview the TMPR3911/12 is the single-chip, integrated digital assp for the personal digital assistants (pda). figure 1.1.1 shows a block diagram of the overall pda system. the TMPR3911/12 consists of the pda system support logic, integrated with an embedded tx39/h processor core designed by toshiba. the TMPR3911/12 consists of a tx39/h processor core with 4 kbytes of instruction cache memory and 1 kbyte of data cache memory, plus integrated functions for interfacing to numerous system components and external i/o modules. the tx39/h processor core is also augmented with a single-cycle multiply/accumulate module to allow integrated dsp functions, such as a software modem for high- performance standard data and fax protocols. the TMPR3911/12 also contains multiple dma channels and a high-performance and flexible bus interface unit (biu) for providing an efficient means for transferring data between external system memory, cache memory, the processor core, and external i/o modules. the types of external memory devices supported include dynamic random access memory (dram), synchronous dynamic random access memory (sdram), static random access memory (sram), flash memory, read- only memory (rom), and expansion cards (pcmcia and/or magiccard). the TMPR3911/12 also contains a system interface module (sim) containing integrated functions for interfacing to numerous external i/o modules such as liquid crystal displays (lcd?s), the tc35143 (which handles most of the analog functions of the system, including sound and telecom codecs and touchscreen adc), isdn/high-speed serial, infrared, wireless peripherals, magicbus, etc. lastly, the TMPR3911/12 contains support for implementation of power management for pda system, whereby various TMPR3911/12 internal modules and external subsystems can be individually (under software control) powered up and down. the TMPR3911/12 contains the following overall features: ? high level of integration on a single chip, small board space, low pin count, low power, and high performance ? plastic lqfp208-pin package (tmpr3912au-92) fbga 217-pin package (tmpr3912xb-92) plastic lqfp176-pin package (TMPR3911bu) fbga177-pin package (TMPR3911bxb) ? 32-bit tx39/h processor core, cache memory, multiply-accumulate module, multi-channel dma controller, bus interface unit and memory controller, power management, and other peripheral subsystems all on a single integrated chip ? minimal number of inter-chip connections ? maximum operation frequency: 58 mhz (TMPR3911bu and TMPR3911bxb) 92 mhz (tmpr3912au-92 and xb-92) ? low power consumption ? entire TMPR3911/12 operation is 3.3 v (in case of TMPR3911bu/bxb, i/o: 3.3 v, internal: 2.6 v) ? real-time clock based on 32.768 khz reference ? processor core clock stop state for low standby current ? power-down modes for individual internal peripheral modules www.datasheet.in chapter 1 TMPR3911/12 overview 1-2 ac adapter magiccard(s) tc35143f (analog front end) 64-pin qfp TMPR3911/12 32-bit bus id rom high speed serial port lcd backup (lithium) power supply magicbus jack 3.3 v thermistor rf xceiver sysclk 32 khz phone jack or daa ir touchscreen (resistive) isdn or other peripherals main tx39/h processor core (future option) 1-2 pcmcia slots memory protection i-cache/ram timers real-time clock lcd interface s erial i / f and magicbus dram/sdram interface pcmcia/ rom i/f d-cache/ ram 1 to 64 mbytes rom 1 to 16 (32) mbytes ( s ) dram t figure 1.1.1 pda block diagram www.datasheet.in chapter 1 TMPR3911/12 overview 1-3 figure 1.1.2 shows a block diagram of the TMPR3911/12. the key functions and features for each TMPR3911/12 module are itemized below. processor core module ? tx39/h processor core ? full 32-bit operation (registers, instructions, addresses, etc.) ? 32 general purpose 32-bit registers; 32-bit program counter ? mips risc instruction set architecture (isa) supported ? translation look-aside buffer (tlb) (4k page size, 32 entries) ? on-chip cache ? 4 kbyte instruction cache (i-cache) ? physical address tag and valid bit per cache line ? programmable burst size ? instruction streaming mode supported ? direct-mapped ? 1 kbyte data cache (d-cache) ? physical address tag and valid bit per cache line ? programmable burst size ? write-through ? two-way set associative ? cache address snoop mode supported for dma ? 4-level deep write buffer ? high-speed multiplier/accumulator ? on-chip hardware multiplier ? supports 32 32 multiplier operations, with 64-bit accumulator ? existing multiply instructions are enhanced and new multiply and add instructions are added to the r3000a instruction set to improve the performance of dsp applications ? processor core interface ? handles data bus, address bus, and control interface between processor core and rest of the TMPR3911/12 logic www.datasheet.in chapter 1 TMPR3911/12 overview 1-4 to high speed serial to general purpose i/o data addr tx39/h processor core with tlb i cache 4 kbyte control to memory sysclk 32 khz to ir spi module power module interrupt module uart module (dual uart) ir module chi module to uart system interface unit (siu) module arbitration/dma/addr decode sib module addr data system interface module (sim) clock module timer module ( + rtc) io module magicbus module video module d cache 1 kbyte mac to magicbus to lcd to tc35143f tx39/h processor core addr data bus interface (biu) module (s) dram/pcmcia/rom addr data tag to power supply figure 1.1.2 TMPR3911/12 block diagram www.datasheet.in chapter 1 TMPR3911/12 overview 1-5 biu module ? system memory and the TMPR3911/12 bus interface unit (biu) ? supports up to 2 banks of physical memory ? supports self-refreshing dram and sdram ? programmable parameters for each bank of dram or sdram (row/column address configuration, refresh, burst modes, etc.) ? programmable chip select memory access ? 4 programmable (size, wait states, burst mode control) memory device and general purpose chip selects ? available for system rom, sram, flash ? available for external port expansion registers ? 4 programmable (wait states, burst mode control) magiccard or general purpose chip selects ? the TMPR3911/12 provides the chip select and card detect signals ? supports card insertion/removal timeouts ? supports up to 2 identical pcmcia ports ? the TMPR3911/12 and the tc35143 provide the control signals and accepts the status signals ? appropriate connector keying and level-shifting buffers required for 3.3 v versus 5 v pcmcia interface implementations siu module ? multi-channel 32-bit dma controller and system interface unit (siu) ? independent dma channels for video, magicbus, sib to/from tc35143 audio/telecom codecs, high- speed serial port, ir uart, and general purpose uart ? address decoding for submodules within system interface module (sim) www.datasheet.in chapter 1 TMPR3911/12 overview 1-6 clock module ? the TMPR3911/12 supports system-wide single crystal configuration, besides the 32 khz rtc xtal (reduces cost, power, and board space) ? common crystal rate divided to generate clock for cpu, video, sound, telecom, uarts, etc. ? independent enabling or disabling of individual clocks under software control, for power management chi module ? high-speed serial concentration highway interface (chi) contains logic for interfacing to external full- duplex serial time-division-multiplexed (tdm) communication peripherals ? supports isdn line interface chips and other pcm/tdm serial devices ? chi interface is programmable (number of channels, frame rate, bit rate, etc.) to provide support for a variety of formats ? supports data rates up to 4.096 mbps ? independent dma support for chi receive and transmit interrupt module ? contains logic for individually enabling, reading, and clearing all TMPR3911/12 interrupt sources ? interrupts generated from internal TMPR3911/12 modules or from edge transitions on external signal pins www.datasheet.in chapter 1 TMPR3911/12 overview 1-7 i/o module ? contains support for reading and writing the 7 bi-directional general purpose i/o pins and the 32 bi- directional multi-function i/o pins ? each i/o port can generate a separate positive and negative edge interrupt ? independently configurable i/o ports allow the TMPR3911/12 to support a flexible and wide range of system applications and configurations ir module ? ir consumer mode ? allows control of consumer electronic devices such as stereos, tvs, vcrs, etc. ? programmable pulse parameters ? external analog led circuitry ? irda communication mode ? allows communication with other irda devices such as fax machines, copiers, printers, etc. ? supported by the uart module within the TMPR3911/12 ? external analog receiver preamplifier and led circuitry ? data rate = up to 115 kbps at 1 meter ? ir fsk communication mode ? supported by the uart module within the TMPR3911/12 ? external analog ir chip(s) perform frequency modulation to generate the desired ir communication mode protocol ? data rate = up to 36000 bps at 3 meters ? carrier detect state machine ? periodically enables ir receiver to check if a valid carrier is present www.datasheet.in chapter 1 TMPR3911/12 overview 1-8 magicbus module ? synchronous, serial 2-wire (clock and data), half-duplex communications protocol ? supports low-cost, low-power peripherals ? supports maximum data rate of 14.75 mbps ? dma support for magicbus receive and transmit power module ? power-down modes for individual internal peripheral modules ? serial (spi port) power supply control interface supported ? power management state machine has 3 states: running, dozing and sleep sib module ? the TMPR3911/12 contains holding and shift registers to support the serial interface to the tc35143 asic and/or other optional codec devices ? interface compatible with slave mode 3 of the crystal cs4216 codec ? synchronous, frame-based protocol ? the TMPR3911/12 always master source of clock and frame frequency and phase ; programmable clock frequency ? each sib frame consists of 128 clock cycles, further divided into 2 subframes or words of 64 bits each (supports up to 2 devices simultaneously) ? independent dma support for audio receive and transmit, telecom receive and transmit ? supports 8-bit or 16-bit mono telecom formats ? supports 8-bit or 16-bit mono or stereo audio formats ? independently programmable audio and telecom sample rates ? cpu read/write registers for subframe control and status www.datasheet.in chapter 1 TMPR3911/12 overview 1-9 spi module ? provides interface to spi peripherals and devices ? full-duplex, synchronous serial data transfers (data in, data out, and clock signals) ? the TMPR3911/12 supplies dedicated chip select and interrupt for an spi interface serial power supply ? 8-bit or 16-bit data word lengths for the spi interface ? programmable spi baud rate timer module ? real time clock (rtc) and timer ? 40-bit counter (30.517 s granularity); maximum uninterrupted time = 388.36 days ? 40-bit alarm register (30.517 s granularity) ? 16-bit periodic timer (0.868 s granularity at sysclk = 75 mhz); maximum timeout = 56.8 ms ? interrupts on alarm, timer, and prior to rtc roll-over www.datasheet.in chapter 1 TMPR3911/12 overview 1-10 uart module ? 2 independent full-duplex uarts ? programmable baud rate generator ? uartb port used for serial control interface to external ir module ? uarta port used for general purpose serial control interface ? uarta and uartb dma support for receive and transmit video module ? bit-mapped graphics ? supports monochrome, gray scale, or color modes ? time-based dithering algorithm for gray scale and color modes ? supports multiple screen sizes ? supports split and non-split displays ? variable size and relocatable video buffer ? dma support for fetching image data from video buffer www.datasheet.in chapter 1 TMPR3911/12 overview 1-11 1.2 references (1) mips risc architecture, gerry kane and joe heinrich, prentice hall, 1992 this book is a comprehensive reference for the mips risc instruction set architecture (isa). this book also describes implementation-specific architectural features for each of the mips risc processor families. this book includes descriptions of cpu architecture, memory management, cache architecture, instruction set summary, exception processing, floating-point unit, and assembly language programming. (2) pc card standard, release 2.01, personal computer memory card international association, november 1992 this document provides a description of the standard for pc card interchangeability. this includes card and socket physical and mechanical specifications, connector pin description and electrical interface specifications, card data formats and header organization, and execute in place specifications. this is not a general magic document, and availability of this document is controlled by the personal computer memory card international association. (3) tx39 family users manual, toshiba (4) computer architecture: a quantitative approach second edition john l hennessy & david a patterson morgan kaufmann publishers, inc. isbn 1-55860-329-8 (5) see mips run dominic sweetman morgan kaufmann publishers, inc. isbn 1-55860-410-3 (6) mips technologies inc. publications http://www.mips.com/publications/ (7) sgi document archive ftp://sgigate.sgi.com/pub/doc/ www.datasheet.in chapter 1 TMPR3911/12 overview 1-12 www.datasheet.in chapter 2 pin descriptions 2-1 2. pin descriptions 2.1 overview the tmpr3912 contains 208 pins (lqfp) or 217 pins (fbga) consisting of input, output, bi-directional, and power and ground pins. the TMPR3911 contains 176 pins (lqfp) or 177 pins (fbga) consisting of input, output, bi-directional, and power and ground pins. the only difference between TMPR3911 and tmpr3912 is pin counts of power and ground pins. these pins are used to support various functions. the following sections describe the function of each pin including any special power-down considerations for each pin. www.datasheet.in chapter 2 pin descriptions 2-2 2.2 pins the tmpr3912 contains 137 signal pins, 3 spare pins, 34 power pins, and 34 ground pins. the TMPR3911 contains 137 signal pins, 3 spare pins, 19 power pins and 17 ground pins. of the 137 signal pins, 32 of them are multi-function and can be independently programmed either as io ports or for an alternate standard/normal function. as an io port, any of these pins can be programmed as an input or output port, with the capability of generating a separate positive and negative edge interrupt. see section 2.3 for a summary of the multi-function io ports versus their standard functions. 2.2.1 memory pins d[31:0]: input/output these pins are the data bus signals for the system. these pins are normally outputs and only become inputs during reads, thus no resistors are required since the bus will only float for a short period of time during bus turn-around. for more information, see section 4.3.2. a[12:0]: output these pins are the address bus signals for the system. the address lines are multiplexed and can be connected directly to sdram and dram devices. to generate the full 26-bit address for static devices, an external latch must be used to latch the signals using the ale signal. for static devices, address bits 25:13 are provided by the external latch and address bits 12:0 (directly connected from the TMPR3911/12?s address bus) are held afterward by the TMPR3911/12 for the remainder of the address bus cycle. ale: output this pin is used as the address latch enable signal to latch a[12:0] using an external latch, for generating the upper address bits 25:13. rd*: output this pin is used as the read signal for static devices. this signal is asserted for reads from mcs3-0*, cs3-0*, card2cs* and card1cs* for memory and attribute space. www.datasheet.in chapter 2 pin descriptions 2-3 we*: output this pin is used as the write signal for the system. this signal is asserted for writes to mcs3-0*, cs3-0*, card2cs* and card1cs* for memory and attribute space, and for writes to dram and sdram. cas0* (we0*): output this pin is used as the cas signal for sdrams, the cas signal for d[7:0] for drams, and the write enable signal for d[7:0] for static devices. cas1* (we1*): output this pin is used as the cas signal for d[15:8] for drams and the write enable signal for d[15:8] for static devices. cas2* (we2*): output this pin is used as the cas signal for d[23:16] for drams and the write enable signal for d[23:16] for static devices. also used as the bank select signal for sdram (applies only to tmpr3912xb-92/au-92) cas3* (we3*): output this pin is used as the cas signal for d[31:24] for drams and the write enable signal for d[31:24] for static devices. ras0*: output this pin is used as the ras signal for sdrams and the ras signal for bank0 drams. ras1* (dcs1*): output this pin is used as the chip select signal for bank1 sdrams and the ras signal for bank1 drams. dcs0*: output this pin is used as the chip select signal for bank0 sdrams. dcke: output this pin is used as the clock enable for sdrams. www.datasheet.in chapter 2 pin descriptions 2-4 dclkin: input this pin must be tied externally to the dclkout signal and is used to match skew for the data input when reading from sdram and dram devices. dclkout: output this pin is the clock for the sdrams. dqmh: output this pin is the upper data mask for a 16-bit sdram configuration. dqml: output this pin is the lower data mask for a 16-bit sdram or 8-bit sdram configuration. cs3-0*: output these pins are the chip select 3 through 0 signals. they can be configured to support either 32- bit or 16-bit ports. mcs3-0*: output these pins are the magiccard chip select 3 through 0 signals. they only support 16-bit ports. card2csh*, l*: output these pins are the chip select signals for pcmcia card slot 2. card1csh*, l*: output these pins are the chip select signals for pcmcia card slot 1. cardreg*: output this pin is the reg* signal for the pcmcia cards. cardiord*: output this pin is the iord* signal for the pcmcia io cards. www.datasheet.in chapter 2 pin descriptions 2-5 cardiowr*: output this pin is the iowr* signal for the pcmcia io cards. carddir*: output this pin is used to provide the direction control for bi-directional data buffers used for the pcmcia slot(s). this signal will assert whenever card2csh* or card2csl* or card1csh* or card1csl* is asserted and a read transaction takes place. card2wait*: input this pin is the card wait signal from pcmcia card slot 2. card1wait*: input this pin is the card wait signal from pcmcia card slot 1. www.datasheet.in chapter 2 pin descriptions 2-6 2.2.2 bus arbitration pins dreq*: input this pin is used to request external arbitration. the TMPR3911/12 memory transactions are halted and certain memory signals will be tri-stated when dgrnt* is asserted in order to allow an external master to access memory. dgrnt*: output this pin is asserted in response to dreq* to inform the external test logic or bus master that it can now begin to drive signals. 2.2.3 clock pins sysclkin: input this pin should be connected along with sysclkout to an external crystal which is the main TMPR3911/12 clock source. sysclkout: output this pin should be connected along with sysclkin to an external crystal which is the main TMPR3911/12 clock source. c32kin: input this pin along with c32kout should be connected to a 32.768 khz crystal. c32kout: output this pin along with c32kin should be connected to a 32.768 khz crystal. bc32k: output this pin is a buffered output of the 32.768 khz clock. www.datasheet.in chapter 2 pin descriptions 2-7 2.2.4 chi pins chifs: input/output this pin is the chi frame synchronization signal. this pin is available for use in one of two modes. as an output, this pin allows the TMPR3911/12 to be the master chi sync source. as an input, this pin allows an external peripheral to be the master chi sync source and the TMPR3911/12 chi module will slave to this external sync. chiclk: input/output this pin is the chi clock signal. this pin is available for use in one of two modes. as an output, this pin allows the TMPR3911/12 to be the master chi clock source. as an input, this pin allows an external peripheral to be the master chi clock source and the TMPR3911/12 chi module will slave to this external clock. chidout: output this pin is the chi serial data output signal. chidin: input this pin is the chi serial data input signal. 2.2.5 io pins io[6:0]: input/output these pins are general purpose input/output ports. each port can be independently programmed as an input or output port. each port can generate a separate positive and negative edge interrupt. each port can also be independently programmed to use a 16 to 24 ms debouncer. mfio[1:0]: input/output these pins are multi-function input/output ports. each port can be independently programmed as an input or output port, or can be programmed for multi-function use to support test signals (for debugging purposes only). each port can generate a separate positive and negative edge interrupt. note that 30 other multi-function pins are available for usage as multi-function input/output ports. these pins are named after their respective standard/normal function and are not listed here. www.datasheet.in chapter 2 pin descriptions 2-8 2.2.6 magicbus pins mbusclk: input/output this pin is the bi-directional magicbus clock signal. mbusclk is an input signal whenever the TMPR3911/12 is in the slave mode and is an output signal whenever the TMPR3911/12 is in the master mode. mbusdata: input/output this pin is the bi-directional magicbus data signal. mbusdata is an input signal whenever the TMPR3911/12 is in the slave mode and is an output signal whenever the TMPR3911/12 is in the master mode. mbusint: input this pin is the magicbus interrupt signal. this signal is used to interrupt the TMPR3911/12 whenever a peripheral has been attached to or detached from the bus, or whenever a peripheral has initiated an interrupt event. 2.2.7 reset pins cpures*: input this pin is used to reset the processor core. this pin should be connected to a switch for initiating a reset in the event that a software problem might hang the processor core. the pin should also be pulled up to vstandby (external signal) through an external pull-up resistor. pon*: input this pin serves as the power on reset signal for the TMPR3911/12. this signal must remain low when vstandby (external signal) is asserted until vstandby is stable. once vstandby is asserted, this signal should never go low unless all power is lost in the system. www.datasheet.in chapter 2 pin descriptions 2-9 2.2.8 power module pins onbutn: input asserting this signal will cause pwrcs to be asserted if the pwrok signal is high. pwrcs: output this signal is asserted automatically if the onbutn signal is asserted when the pwrok signal is high. clearing the pwrcs bit in the power control register by software deasserts this signal. pwrok: input this pin should be asserted when the source of power is stable. when the pwroknmi bit in the interrupt status 6 register is set, the deassertion of the pwrok signal causes the nmi (non maskable interrupt). pwrint: input the rising edge and falling edge of signal to this pin causes pwrint interrupt request. vcc3: input this pin should be asserted when the source of power for external circuit is stable. asserting this pin starts oscillating the internal clock. for more details of these pins, see chapter 12. www.datasheet.in chapter 2 pin descriptions 2-10 2.2.9 sib pins sibdin: input this pin is used for serial input to the sib module. sibdout: output this pin is used for serial output from the sib module. sibsclk: output this pin is the clock for sib interface. sibsync: output this pin is the frame synchronization signal for sib interface. this frame sync is asserted for one clock cycle immediately before each frame starts and all devices connected to the sib monitor sibsync to determine when they should transmit or receive data. sibirq: input the rising edge and falling edge of signal to this pin causes sibirq interrupt request. sibmclk: input/output this pin is the master clock source for the sib module. www.datasheet.in chapter 2 pin descriptions 2-11 2.2.10 spi pins spiclk: output this pin is used to clock data in and out of the spi slave device. spiout: output this pin contains the data that is shifted into the spi slave device. spiin: input this pin contains the data that is shifted out of the spi slave device. 2.2.11 uart and ir pins txd: output this pin is the uart transmit signal from the uarta module. rxd: input this pin is the uart receive signal to the uarta module. irout: output this pin is the uart transmit signal from the uartb module or the consumer ir output signal if consumer ir mode is enabled. irin: input this pin is the uart receive signal to the uartb module. rxpwr: output this pin is the receiver power output control signal to the external communication ir analog circuitry. cardet: input this pin is the carrier detect input signal from the external communication ir analog circuitry. www.datasheet.in chapter 2 pin descriptions 2-12 2.2.12 video pins frame: output this pin is the frame synchronization pulse signal between the video module and the lcd, and is used by the lcd to return its pointers to the top of the display. the video module asserts frame after all the lines of the lcd have been shifted and transferred, producing a full frame of display. df: output this pin is the ac signal for the lcd. since lcd plasma tends to deteriorate whenever subjected to a dc voltage, the df signal is used by the lcd to alternate the polarity of the row and column voltages used to turn the pixels on and off. the df signal can be configured to toggle on every frame or can be configured to toggle every programmable number of load signals. load: output this pin is the line synchronization pulse signal between the video module and the lcd, and is used by the lcd to transfer the contents of its horizontal line shift register to the lcd panel for display. the video module asserts load after an entire horizontal line of data has been shifted into the lcd. cp: output this pin is the clock signal for the lcd. data is pushed by the video module on the rising edge of cp and sampled by the lcd on the falling edge of cp. vdat[3:0]: output these pins are the data for the lcd. these signals are directly connected to the lcd for 4-bit non-split displays. for 4-bit split and 8-bit non-split displays, an external register is required to demultiplex the 4-bit data into the desired 8 parallel data lines needed for the lcd. dispon: output this pin is the display-on enable signal for the lcd. viddone: output this pin is used to externally synchronize events to periods when the video is not shifting. www.datasheet.in chapter 2 pin descriptions 2-13 2.2.13 endian pin endian: input this pin is used to select the endianness. the high level input sets the endianness to the big endian. the low level input sets the endianness to the little endian. 2.2.14 test pins testaiu: input if this pin is set to low during reset, rom data bus width will be 16 bits wide. if this pin is set to high during reset, rom data bus width will be 32 bits wide. when the dreq* signal is asserted to request external arbitration, this pin must be set to low. testcpu: input connect to gnd. testin: input connect to gnd. 2.2.15 spare pins nc3-1: no connect these pins are reserved for future use and should be left unconnected. 2.2.16 power supply pins vdd: + 3.3 v these pins are the power pins. (in case of tmrp3912au-92 and tmrp3912xb-92) vss: gnd these pins are the ground pins for the TMPR3911/12. vddh: + 3.3 v these pins are the power pins for i/o. (in case of TMPR3911bu and TMPR3911bxb) vddl: + 2.6 v these pins are the power pins for internal logic. (in case of TMPR3911bu and TMPR3911bxb) vdd (pll): + 2.6 v these pins are the power pins for pll. (in case of TMPR3911bu and TMPR3911bxb) vss (pll): gnd these pins are the ground pins for pll. (in case of TMPR3911bu and TMPR3911bxb) www.datasheet.in chapter 2 pin descriptions 2-14 2.3 pin mode this section contains tables summarizing various aspects of the pin usage for the TMPR3911/12. table 2.3.1 lists the standard versus multi-function usage for each TMPR3911/12 pin, if applicable. the column showing the multi-function select indicates the corresponding bit in the miosel register, as well as the default configuration of each multi-function pin during reset. the ?bus arb state? column shows which pins are tri-stated whenever the dgrnt* signal is asserted in response to a dreq* (external bus arbitration request). table 2.3.1 TMPR3911/12 standard and multi-function pin mode (1/3) multi-function select 1 = multi-function mode 0 = standard function mode TMPR3911/12 pin standard function (i = input, o = output) multi-function miosel reset state bus arb state d[31:0] d[31:0] (i/o) ? ? ? hi-z a[12:0] a[12:0] (i/o) ? ? ? hi-z ale ale (o) ? ? ? hi-z rd * rd * (o) ? ? ? hi-z we * we * (o) ? ? ? hi-z cas0 * (we0 * ) cas0 * (o) ? ? ? hi-z cas1 * (we1 * ) cas1 * (o) ? ? ? hi-z cas2 * (we2 * ) cas2 * (o) ? ? ? hi-z cas3 * (we3 * ) cas3 * (o) ? ? ? hi-z ras0 * ras0 * (o) ? ? ? hi-z ras1 * (dcs1) * ras1 * (o) ? ? ? hi-z dcs0 * dcs0 * (o) ? ? ? hi-z dcke dcke (o) ? ? ? hi-z dclkin dclkin (i) ? ? ? ? dclkout dclkout (o) ? ? ? hi-z dqmh dqmh (o) ? ? ? hi-z dqml dqml (o) ? ? ? hi-z dreq * dreq * (i) mio[27] miosel[27] 0 ? dgrnt * dgrnt * (o) mio[26] miosel[26] 0 ? sysclkin sysclkin (i) ? ? ? ? sysclkout sysclkout (o) ? ? ? ? c32kin c32kin (i) ? ? ? ? c32kout c32kout (o) ? ? ? ? bc32k bc32k (o) mio[25] miosel[25] 1 ? vdat[3] vdat[3] (o) ? ? ? ? vdat[2] vdat[2] (o) ? ? ? ? vdat[1] vdat[1] (o) ? ? ? ? vdat[0] vdat[0] (o) ? ? ? ? cp cp (o) ? ? ? ? load load (o) ? ? ? ? df df (o) ? ? ? ? frame frame (o) ? ? ? ? dispon dispon (o) ? ? ? ? pwrcs pwrcs (o) ? ? ? ? pwrint pwrint (i) ? ? ? ? www.datasheet.in chapter 2 pin descriptions 2-15 table 2.3.2 TMPR3911/12 standard and multi-function pin mode (2/3) multi-function select 1 = multi-function mode 0 = standard function mode TMPR3911/12 pin standard function (i = input, o = output) multi-function miosel reset state bus arb state pwrok pwrok (i) ? ? ? ? onbutn onbutn (i) ? ? ? ? cpures * cpures * (i) ? ? ? ? pon * pon * (i) ? ? ? ? mbusclk mbusclk (i/o) ? ? ? ? mbusdata mbusdata (i/o) ? ? ? ? mbusint mbusint (i) ? ? ? ? txd txd (o) mio[24] miosel[24] 0 ? rxd rxd (i) mio[23] miosel[23] 0 ? cs0 * cs0 * (o) ? ? hi-z cs1 * cs1 * (o) mio[22] miosel[22] 0 ? cs2 * cs2 * (o) mio[21] miosel[21] 0 ? cs3 * cs3 * (o) mio[20] miosel[20] 0 mcs0 * mcs0 * (o) mio[19] miosel[19] 1 ? mcs1 * mcs1 * (o) mio[18] miosel[18] 1 ? mcs2 * mcs2 * (o) mio[17] miosel[17] 1 ? mcs3 * mcs3 * (o) mio[16] miosel[16] 1 ? chifs chifs (i/o) mio[31] miosel[31] 1 ? chiclk chiclk (i/o) mio[30] miosel[30] 1 ? chidout chidout (o) mio[29] miosel[29] 1 ? chidin chidin (i) mio[28] miosel[28] 1 ? vcc3 vcc3 (i) ? ? ? ? io6 io6 (i/o) ? ? ? ? io5 io5 (i/o) ? ? ? ? io4 io4 (i/o) ? ? ? ? io3 io3 (i/o) ? ? ? ? io2 io2 (i/o) ? ? ? ? io1 io1 (i/o) ? ? ? ? io0 io0 (i/o) ? ? ? ? spiclk spiclk (o) mio[15] miosel[15] 0 ? spiout spiout (o) mio[14] miosel[14] 0 ? spiin spiin (i) mio[13] miosel[13] 0 ? sibsync sibsync (o) ? ? ? ? sibdout sibdout (o) ? ? ? ? sibdin sibdin (i) ? ? ? ? sibmclk sibmclk (i/o) mio[12] miosel[12] 0 ? sibsclk sibsclk (o) ? ? ? ? sibirq sibirq (i) ? ? ? ? rxpwr rxpwr (o) ? ? ? ? cardet cardet (i) ? ? ? ? irout irout (o) ? ? ? ? irin irin (i) ? ? ? ? testaiu testaiu (i) ? ? ? ? testcpu testcpu (i) ? ? ? ? testin testin (i) ? ? ? ? viddone viddone (o) ? ? ? ? www.datasheet.in chapter 2 pin descriptions 2-16 table 2.3.3 TMPR3911/12 standard and multi-function pin mode (3/3) multi-function select 1 = multi-function mode 0 = standard function mode TMPR3911/12 pin standard function (i = input, o = output) multi-function miosel reset state bus arb state cardreg * cardreg * (o) (showdino cs * ) mio[11] miosel[11] 1 ? cardiowr * cardiowr * (o) mio[10] miosel[10] 1 ? cardiord * cardiord * (o) mio[9] miosel[9] 1 ? card1csl * card1csl * (o) mio[8] miosel[8] 1 ? card1csh card1csh * (o) mio[7] miosel[7] 1 ? card2csl * card2csl * (o) mio[6] miosel[6] 1 ? card2csh * card2csh * (o) mio[5] miosel[5] 1 ? card1wait * card1wait * (i) mio[4] miosel[4] 1 ? card2wait * card2wait * (i) mio[3] miosel[3] 1 ? carddir * carddir * (o) mio[2] miosel[2] 1 ? mfio[1] reserved mio[1] miosel[1] 1 ? mfio[0] reserved mio[0] miosel[0] 1 ? endian endian (i) ? ? ? ? nc[3:1] spare ? ? ? ? vdd + 3.3 v ( * 1) ? ? ? ? vss gnd ? ? ? ? vddh + 3.3 v ( * 2) ? ? ? ? vddl + 2.6 v ( * 2) ? ? ? ? * 1) in case of tmpr3912au-92 and tmpr3912xb-92 * 2) in case of TMPR3911bu and mtpr3911bxb www.datasheet.in chapter 2 pin descriptions 2-17 table 2.3.4 lists various power-down states and conditions for each TMPR3911/12 pin. the ?power-down control? column shows the conditions which trigger a power-down for each respective pin. this column also shows the reset state for each of these conditions. the ?pon* state? column defines the state of each pin at power-on reset (pon*). this condition is defined as initial power up of the TMPR3911/12. this state is entered after power is applied for the very first time (vstandby is turned on but vcc3 is still turned off). see figure 12.2.2. the ?1st-time power-up state? column defines the state of each pin after power-up. this mode is defined as vcc3 applied to the entire system and is initiated by the user pressing the onbutn while in the power- on reset (pon*) state. see figure 12.2.2. the ?power-down state? column defines the state of each pin during power-down mode. table 2.3.4 TMPR3911/12 power-down pin mode (1/3) TMPR3911/12 pin pon * state 1st time power-up state power-down state power-down control d[31:0] low low low mempowerdown a[12:0] low low low mempowerdown ale low low low x rd * low hi low powerdown we * low low low mempowerdown cas0 * (we0 * ) low low low mempowerdown cas1 * (we1 * ) low low low mempowerdown cas2 * (we2 * ) low low low mempowerdown cas3 * (we3 * ) low low low mempowerdown ras0 * low low low mempowerdown ras1 * (dcs1 * ) low low low mempowerdown dcs0 * low low low mempowerdown dcke low low low mempowerdown dclkin * in in in x dclkout low low low mempowerdown dqmh low low low mempowerdown dqml low low low mempowerdown dreq pull-down in selectable powerdown & miopd[27] dgrnt * low hi selectable powerdown & miopd[26] sysclkin osc off osc on osc off powerdown sysclkout osc off osc on osc off powerdown c32kin osc on osc on osc on x c32kout osc on osc on osc on x bc32k pull-down in selectable powerdown & miopd[25] vdat[3] low low low video module disabled vdat[2] low low low video module disabled vdat[1] low low low video module disabled vdat[0] low low low video module disabled powerdown = (vccon & vcc3) * vccon: a bit in the power control register. vcc3: an input signal. mempowerdown: a bit in the memory configration 4 register. selectable: see table 9.2.2 and 9.2.3. www.datasheet.in chapter 2 pin descriptions 2-18 table 2.3.5 TMPR3911/12 power-down pin mode (2/3) TMPR3911/12 pin pon * state 1st time power-up state power-down state power-down control cp low low low video module disabled load low low low video module disabled df low low low video module disabled frame low low low video module disabled dispon low low low video module disabled pwrcs low hi low x pwrint in in in x pwrok in in in x onbutn in in in x cpures * in in in x pon * in in in x mbusclk low low low magicbus module disabled mbusdata low low low magicbus module disabled mbusint in in in x txd low low selectable powerdown & miopd[24] rxd pull-down in selectable powerdown & miopd[23] cs0 * pull-down hi pull-down powerdown cs1 * pull-down hi selectable powerdown & miopd[22] cs2 * pull-down hi selectable powerdown & miopd[21] cs3 * pull-down hi selectable powerdown & miopd[20] mcs0 * pull-down in selectable powerdown & miopd[19] mcs1 * pull-down in selectable powerdown & miopd[18] mcs2 * pull-down in selectable powerdown & miopd[17] mcs3 * pull-down in selectable powerdown & miopd[16] chifs pull-down in selectable powerdown & miopd[31] chiclk pull-down in selectable powerdown & miopd[30] chidout pull-down in selectable powerdown & miopd[29] chidin pull-down in selectable powerdown & miopd[28] vcc3 pull-down in pull-down powerdown io6 pull-down in selectable powerdown & iopd[6] io5 pull-down in selectable powerdown & iopd[5] io4 pull-down in selectable powerdown & iopd[4] io3 pull-down in selectable powerdown & iopd[3] io2 pull-down in selectable powerdown & iopd[2] io1 pull-down in selectable powerdown & iopd[1] io0 pull-down in selectable powerdown & iopd[0] spiclk low low selectable powerdown & miopd[15] spiout low low selectable powerdown & miopd[14] spiin pull-down in selectable powerdown & miopd[13] sibync low low low powerdown sibdout low low low powerdown sibdin pull-down in pull-down powerdown sibmclk pull-down in selectable powerdown & miopd[12] sibsclk low low low powerdown sibirq pull-down in pull-down powerdown powerdown = (vccon & vcc3) * vccon: a bit in the power control register. vcc3: an input signal. mempowerdown: a bit in the memory configration 4 register. selectable: see table 9.2.2 and 9.2.3. www.datasheet.in chapter 2 pin descriptions 2-19 table 2.3.6 TMPR3911/12 power-down pin mode (3/3) TMPR3911/12 pin pon * state 1st time power-up state power-down state power-down control rxpwr low low low powerdown cardet pull-down in pull-down powerdown irout low low low powerdown irin pull-down in pull-down powerdown testaiu in in in x testcpu in in in x testin in in in x viddone low low low x cardreg * pull-down in selectable powerdown & miopd[11] cardiowr * pull-down in selectable powerdown & miopd[10] cardiord * pull-down in selectable powerdown & miopd[9] card1csl * pull-down in selectable powerdown & miopd[8] card1csh * pull-down in selectable powerdown & miopd[7] card2csl * pull-down in selectable powerdown & miopd[6] card2csh * pull-down in selectable powerdown & miopd[5] card1wait * pull-down in selectable powerdown & miopd[4] card2wait * pull-down in selectable powerdown & miopd[3] carddir * pull-down in selectable powerdown & miopd[2] mfio[1] in in selectable powerdown & miopd[1] mfio[0] in in selectable powerdown & miopd[0] endian in in in x nc[3:1] x x x x vdd 19each/34each xxx x vss 17each/34each xxx x powerdown = (vccon & vcc3) * vccon: a bit in the power control register. vcc3: an input signal. mempowerdown: a bit in the memory configration 4 register. selectable: see table 9.2.2 and 9.2.3. www.datasheet.in chapter 2 pin descriptions 2-20 2.4 pin assignment 2.4.1 pin assignment (in case of tmpr3912au-92 and tmpr3912xb-92) table 2.4.1 pin assignment (1/3) lqfp no. (tmpr3912) fbga no. i/o signal name lqfp no. (tmpr3912) fbga no. i/o signal name 1a1 ? vdd 45 m2 i/o miox[0] 2 c3 i/o d[0] (d[24]) 46 m3 i/o io[6] 3e5 ? vss 47 l4 i/o io[5] 4 b1 i/o d[1] (d[25]) 48 n1 ? vss 5 c2 i/o d[2] (d[26]) 49 n2 i/o chiclk 6e4 ? vdd 50 m4 i/o chifs 7 c1 i/o d[3] (d[27]) 51 p2 i chidin 8d3 ? vss 52 p1 o chidout 9 d2 i/o d[4] (d[28]) 53 r1 ? vdd 10 f5 ? vdd 54 n3 i rxd 11 d1 i/o d[5] (d[29]) 55 l5 o txd 12 e3 i/o d[6] (d[30]) 56 r2 i/o io[4] 13 e2 ? vss 57 ? nc 14 f4 i/o d[7] (d[31]) 58 m5 i irin 15 e1 ? vss 59 r3 o irout 16 f3 i/o d[8] (d[16]) 60 n4 ? vss 17 f2 ? vdd 61 p4 ? vdd 18 g5 i/o d[9] (d[17]) 62 l6 i cardet 19 f1 i/o d[10] (d[18]) 63 r4 o rxpwr 20 g4 ? vss 64 n5 i/o io[3] 21 g3 i/o d[11] (d[19]) 65 p5 i/o io[2] 22 g2 ? vdd 66 m6 ? vss 23 g1 i/o d[12] (d[20]) 67 r5 o spiclk 24 g6 i/o d[13] (d[21]) 68 n6 i spiin 25 h6 ? vss 69 p6 o spiout 26 h3 i/o d[14] (d[22]) 70 l7 ? vdd 27 h1 i/o d[15] (d[23]) 71 r6 i testcpu 28 h2 ? vdd 72 m7 i testin 29 h4 i endian 73 n7 o viddone 30 j6 i/o miox[1] 74 p7 i testaiu 31 j1 i mbusint 75 r7 ? vss 32 j2 i/o mbusdata 76 k7 i vcc3 33 j3 ? vss 77 l8 o bc32k 34 j4 i/o mbusclk 78 n8 ? vdd 35 j5 ? vdd 79 r8 i c32kln 36 k1 ? vdd 80 p8 o c32kout 37 k2 o sibmclk 81 m8 ? vss 38 k3 ? vss 82 k9 o pwrcs 39 k4 o sibsclk 83 r9 i pwrlnt 40 l1 o sibsync 84 p9 i pwrok 41 l2 i sibdin 85 ? nc 42 l3 o sibdout 86 m9 i onbutn 43 k5 ? vdd 87 l9 i pon * 44 m1 i sibirq 88 r10 i cpures * chapter 2 pin descriptions 2-21 table 2.4.2 pin assignment (2/3) lqfp no. (tmpr3912) fbga no. i/o signal name lqfp no. (tmpr3912) fbga no. i/o signal name 89 p10 ? vdd 137 g13 ? vdd 90 n10 o dispon 138 (g12) i/o d[28] (d[4]) 91 m10 o frame 139 (g11) i/o d[27] (d[3]) 92 r11 ? vss 140 f15 ? vss 93 p11 o df 141 f14 i/o d[26] (d[2]) 94 n11 o load 142 f13 ? vss 95 l10 o cp 143 f12 i/o d[25] (d[1]) 96 r12 ? vss 144 e15 ? vdd 97 p12 ? vdd 145 e14 i/o d[24] (d[0]) 98 n12 o vdat[0] 146 e13 i/o d[23] (d[15]) 99 m11 o vdat[1] 147 f11 ? vdd 100 r13 o vdat[2] 148 d15 i/o d[22] (d[14]) 101 p13 o vdat[3] 149 d14 ? vss 102 m12 ? vss 150 d13 i/o d[21] (d[13]) 103 p14 i/o io[1] 151 e12 ? vdd 104 r14 ? vdd 152 c15 i/o d[20] (d[12]) 105 r15 i card2wait * 153 c14 i/o d[19] (d[11]) 106 n13 o card2csh * 154 d12 ? vss 107 l11 o card2csl * 155 b14 i/o d[18] (d[10]) 108 p15 i/o io[0] 156 b15 ? vdd 109 n14 ? vss (pll) 157 a15 i/o d[17] (d[9]) 110 l12 o cardiord * 158 c13 ? vss 111 n15 o cardiowr * 159 e11 i/o d[16] (d[8]) 112 m13 o cardreg * 160 a14 ? vdd 113 m14 i card1wait * 161 ? nc 114 k11 ? vdd (pll) 162 d11 o cs0 * 115 m15 o carddir * 163 a13 o rd * 116 l13 ? vdd 164 c12 ? vss 117 l14 o card1csl * 165 b12 ? vdd 118 k12 o card1csh * 166 e10 o dgrnt * 119 l15 ? vss 167 a12 i dreq * 120 k13 o mcs3 * 168 c11 o ale 121 k14 o mcs2 * 169 b11 o we * 122 j11 o mcs1 * 170 d10 ? vdd 123 k15 o mcs0 * 171 a11 i/o a[12] 124 j12 o cs3 * 172 c10 i/o a[11] 125 j13 o cs2 * 173 b10 ? vss 126 j14 o cs1 * 174 e9 i/o a[10] 127 j15 ? vdd 175 a10 i/o a[9] 128 j10 i sysclkin 176 d9 ? vdd 129 h11 o sysclkout 177 c9 i/o a[8] 130 h13 ? vss 178 b9 i/o a[7] 131 h15 ? vss 179 a9 ? vss 132 h14 ? vdd 180 f9 i/o a[6] 133 h12 i/o d[31] (d[7]) 181 e8 i/o a[5] 134 g10 i/o d[30] (d[6]) 182 c8 ? vdd 135 g15 ? vss 183 a8 i/o a[4] 136 g14 i/o d[29] (d[5]) 184 b8 ? vss chapter 2 pin descriptions 2-22 table 2.4.3 pin assignment (3/3) lqfp no. (tmpr3912) fbga no. i/o signal name lqfp no. (tmpr3912) fbga no. i/o signal name 185 d8 i/o a[3] 203 d5 ? vss 186 f7 i/o a[2] 204 a3 i dclkin 187 a7 ? vdd 205 b3 o dclkout 188 b7 i/o a[1] 206 d4 ? vdd 189 c7 i/o a[0] 207 b2 o dqmh (dqml) 190 d7 ? vss 208 a2 o dqml (dqmh) 191 e7 ? vss ? b13 ? nc 192 a6 o dcs0 * ? f6 ? nc 193 b6 o ras1 * ? f8 ? nc 194 c6 o ras0 * ? f10 ? nc 195 d6 o cas3 * (cas0 * ) ? g7 ? nc 196 a5 ? vdd ? h5 ? nc 197 b5 o cas2 * (cas1 * ) ? h10 ? nc 198 c5 o cas1 * (cas2 * ) ? k6 ? nc 199 e6 o cas0 * (cas3 * ) ? k8 ? nc 200 a4 ? vss ? k10 ? nc 201 b4 ? vdd ? n9 ? nc 202 c4 o dcke ? p3 ? nc chapter 2 pin descriptions 2-23 2.4.2 pin assignment (in case of TMPR3911bu) table 2.4.4 pin assignment (1/2) no. i/o signal name no. i/o signal name no. i/o signal name 1 ? vddh 41 i/o chiclk 81 ? vss 2 i/o d[0] (d [24]) 42 i/o chifs 82 o vdat[0] 3 i/o d[1] (d [25]) 43 i chidin 83 o vdat[1] 4 i/o d[2] (d [26]) 44 o chidout 84 o vdat[2] 5 i/o d[3] (d [27]) 45 i rxd 85 o vdat[3] 6 ? vss 46 o txd 86 ? vss 7 i/o d[4] (d [28]) 47 i/o io[4] 87 i/o io[1] 8 ? vddl 48 i irin 88 ? vddh 9 i/o d[5] (d [29]) 49 o irout 89 i card2wait * 10 i/o d[6] (d [30]) 50 ? vss 90 o card2csh * 11 i/o d[7] (d [31]) 51 ? vddl 91 o card2csl * 12 i/o d[8] (d [16]) 52 i cardet 92 i/o io[0] 13 i/o d[9] (d [17]) 53 o rxpwr 93 ? vss (pll) 14 i/o d[10] (d [18]) 54 i/o io[3] 94 o cardiord * 15 ? vss 55 i/o io[2] 95 o cardiowr * 16 i/o d[11] (d [19]) 56 o spiclk 96 o cardreg * 17 i/o d[12] (d [20]) 57 i spiin 97 i card1wait * 18 i/o d[13] (d [21]) 58 o spiout 98 ? vdd (pll) 19 i/o d[14] (d [22]) 59 i testcpu 99 o carddir * 20 i/o d[15] (d [23]) 60 i testin 100 o card1csl * 21 vddh 61 o viddone 101 o card1csh * 22 i endian 62 i testaiu 102 o mcs3 * 23 i/o miox[1] 63 i vcc3 103 o mcs2 * 24 i mbusint 64 o bc32k 104 o mcs1 * 25 i/o mbusdata 65 ? vddh 105 o mcs0 * 26 ? vss 66 i c32kln 106 o cs3 * 27 i/o mbusclk 67 o c32kout 107 o cs2 * 28 ? vddh 68 ? vss 108 o cs1 * 29 ? vddl 69 o pwrcs 109 ? vddh 30 o sibmclk 70 i pwrlnt 110 i sysclkin 31 ? vss 71 i pwrok 111 o sysclkout 32 o sibsclk 72 i onbutn 112 ? vss 33 o sibsync 73 i pon * 113 ? vddl 34 i sibdin 74 i cpures * 114 i/o d[31] (d [7]) 35 o sibdout 75 ? vddl 115 i/o d[30] (d [6]) 36 ? nc 76 o dispon 116 i/o d[29] (d [5]) 37 i sibirq 77 o frame 117 i/o d[28] (d [4]) 38 i/o miox[0] 78 o df 118 i/o d[27] (d [3]) 39 i/o io[6] 79 o load 119 ? vss 40 i/o io[5] 80 o cp 120 i/o d[26] (d [2]) chapter 2 pin descriptions 2-24 table 2.4.5 pin assignment (2/2) no. i/o signal name no. i/o signal name no. i/o signal name 121 i/o d[25] (d [1]) 161 i/o a[0] 122 ? vddh 162 ? vss 123 i/o d[24] (d [0]) 163 o dcs0 * 124 i/o d[23] (d [15]) 164 o ras1 * 125 i/o d[22] (d [14]) 165 o ras0 * 126 ? vss 166 o cas3 * (cas0 * ) 127 i/o d[21] (d [13]) 167 o cas2 * (cas1 * ) 128 i/o d[20] (d [12]) 168 o cas1 * (cas2 * ) 129 i/o d[19] (d [11]) 169 o cas0 * (cas3 * ) 130 ? vss 170 ? vddh 131 i/o d[18] (d [10]) 171 o dcke 132 ? vddl 172 i dclkin 133 i/o d[17] (d [9]) 173 o dclkout 134 ? vss 174 ? nc 135 ? nc 175 o dqmh(dqml) 136 i/o d[16] (d [8]) 176 o dqml(dqmh) 137 ? vddh 138 o cs0 * 139 o rd * 140 ? vss 141 ? vddl 142 o dgrnt * 143 i dreq * 144 o ale 145 o we * 146 i/o a[12] 147 i/o a[11] 148 i/o a[10] 149 i/o a[9] 150 ? vddh 151 i/o a[8] 152 i/o a[7] 153 ? vss 154 i/o a[6] 155 i/o a[5] 156 i/o a[4] 157 i/o a[3] 158 i/o a[2] 159 ? vddl 160 i/o a[1] chapter 2 pin descriptions 2-25 2.4.3 pin assignment (in case of TMPR3911bxb) table 2.4.6 pin assignment (1/2) no. i/o signal name no. i/o signal name no. i/o signal name a1 i/o d[1] (d[25]) l3 i sibdin d7 i/o a[3] b1 ? vddh m3 ? nc m7 i vcc3 c1 i/o d[0] (d[24]) n3 i/o io[6] n7 o bc32k d1 i/o d[3] (d[27]) p3 i irin p7 i c32kin e1 i/o d[5] (d[29]) r3 o txd r7 o viddone f1 i/o d[9] (d[17]) a4 o dclkout a8 ? vss g1 i/o d[12] (d[20]) b4 ? vddh b8 i/o a[4] h1 ? vddh c4 o cas1 * (cas2 * )c8i/oa[6] j1 ? vddh d4 ? vss d8 i/o a[5] k1 o sibsync e4 ? vddl m8 o c32kout l1 i sibirq f4 i/o d[10] (d[18]) n8 i testaiu m1 i/o io[5] g4 i/o d[14] (d[22]) p8 ? vss n1 i chidin h4 i/o miox[1] r8 ? vddh p1 o chidout j4 i/o mbusdata a9 i/o a[9] r1 i/o io[4] k4 ? vddl b9 i/o a[7] a2 o dqml (dqmh) l4 o sibsclk c9 i/o a[8] b2 ? nc m4 ? vss d9 ? vddh c2 i/o d[2] (d[26]) n4 i cardet m9 o pwrcs d2 i/o d[6] (d[30]) p4 i/o io[3] n9 i pwrok e2 i/o d[8] (d[16]) r4 o irout p9 i pwrint f2 i/o d[11] (d[19]) a5 o cas0 * (cas3 * )r9ionbutn g2 i endian b5 o cas2 * (cas1 * )a10owe * h2 i mbusint c5 o cas3 * (cas0 * ) b10 i/o a[10] j2 ? vss d5 o ras1 * c10 i/o a[11] k2 ? vss e5 ? nc d10 i/o a[12] l2 o sibdout m5 ? vddl m10 ? vddl m2 i/o miox[0] n5 i/o io[2] n10 i pon * n2 i/o chiclk p5 o spiclk p10 i cpures * p2 i/o chifs r5 o rxpwr r10 o dispon r2 i rxd a6 o ras0 * a11 ? vddl a3 o dqmh (dqml) b6 o dcs0 * b11 o ale b3 i dclkin c6 ? vss c11 i dreq * c3 o dcke d6 i/o a[0] d11 o dgrnt * d3 i/o d[4] (d[28]) m6 o spiout m11 o frame e3 i/o d[7] (d[31]) n6 i testcpu n11 o load f3 ? vss p6 i testin p11 o df g3 i/o d[15] (d[23]) r6 i spiin r11 ? vss h3 i/o d[13] (d[21]) a7 i/o a[1] a12 ? vddh j3 i/o mbusclk b7 i/o a[2] b12 ? vss k3 o sibmclk c7 ? vddl c12 o rd * chapter 2 pin descriptions 2-26 table 2.4.7 pin assignment (2/2) no. i/o signal name no. i/o signal name no. i/o signal name d12 o cs0 * p14 ? vss e12 i/o d[26] (d[2]) r14 ? vddh f12 i/o d[29] (d[5]) a15 ? nc g12 ? vddl b15 ? vddl h12 o sysclkout c15 i/o d[18] (d[10]) j12 o cs2 * d15 i/o d[19] (d[11]) k12 o mcs3 * e15 i/o d[22] (d[14]) l12 ? vdd (pll) f15 i/o d[25] (d[1]) m12 o cardiord * g15 i/o d[28] (d[4]) n12 o cp h15 ? vddh p12 o vdat[0] j15 o mcs0 * r12 o vdat[3] k15 o card1csh * a13 ? vss l15 i card1wait * b13 i/o d[16] (d[8]) m15 ? vss (pll) c13 i/o d[21] (d[13]) n15 o card2csh * d13 i/o d[23] (d[15]) p15 i card2wait * e13 ? vddh r15 o card2csl * f13 i/o d[27] (d[3]) g13 i/o d[30] (d[6]) h13 o cs3 * j13 o cs1 * k13 o mcs2 * l13 o carddir * m13 o cardiowr * n13 o vdat[1] p13 o vdat[2] r13 i/o io[1] a14 i/o d[17] (d[9]) b14 ? vss c14 i/o d[20] (d[12]) d14 ? vss e14 i/o d[24] (d[0]) f14 ? vss g14 i/o d[31] (d[7]) h14 ? vss j14 i sysclkin k14 o mcs1 * l14 o card1csl * m14 o cardreg * n14 i/o io[0] chapter 2 pin descriptions 2-27 2.4.4 TMPR3911bu pin assignment p-lqfp176-2424-0.50a 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 vddh d[0] (d[24]) d[1] (d[25]) d[2] (d[26]) d[3] (d[27]) vss d[4] (d[28]) vddl d[5] (d[29]) d[6] (d[30]) d[7] (d[31]) d[8] (d[16]) d[9] (d[17]) d[10] (d[18]) vss d[11] (d[19]) d[12] (d[20]) d[13] (d[21]) d[14] (d[22]) d[15] (d[23]) vddh endian miox[1] mbusint mbusdata vss mbusclk vddh vddl sibmclk vss sibsclk sibsync sibdin sibdout n.c. sibirq miox[0] io[6] io[5] chiclk chifs chidin chidout 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 vddh io[1] vss vdat[3] vdat[2] vdat[1] vdat[0] vss cp load df frame dispon vddl cpures * pon * onbutn pwrok pwrlnt pwrcs vss c32kout c32kln vddh bc32k vcc3 testaiu viddone testin testcpu spiout spiin spiclk io[2] io[3] rxpwr cardet vddl vss irout irin io[4] txd rxd 1 32 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 vddl d[18] (d[10]) vss d[19] (d[11]) d[20] (d[12]) d[21] (d[13]) vss d[22] (d[14]) d[23] (d[15]) d[24] (d[0]) vddh d[25] (d[1]) d[26] (d[2]) vss d[27] (d[3]) d[28] (d[4]) d[29] (d[5]) d[30] (d[6]) d[31] (d[7]) vddl vss sysclkout sysclkin vddh cs1 * cs2 * cs3 * mcs0 * mcs1 * mcs2 * mcs3 * card1csh * card1csl * carddir * vdd (pll) card1wait * cardreg * cardiowr * cardiord * vss (pll) io[0] card2csl * card2csh * card2wait * 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 d[17] (d[9]) vss n.c. d[16] (d[8]) vddh cs0 * rd * vss vddl dgrnt * dreq * ale we * a[12] a[11] a[10] a[9] vddh a[8] a[7] vss a[6] a[5] a[4] a[3] a[2] vddl a[1] a[0] vss dcs0 * ras1 * ras0 * cas3 * (cas0 * ) cas2 * (cas1 * ) cas1 * (cas2 * ) cas0 * (cas3 * ) vddh dcke dclkin dclkout n.c. dqmh (dqml) dqml (dqmh) www.datasheet.in chapter 2 pin descriptions 2-28 2.4.5 tmpr3912au-92 p-lqfp208-2828-0.50a d[17] (d[9]) vss d[16] (d[8]) vdd nc cs0 * rd * vss vdd dgrnt * dreq * ale we * vdd a[12] a[11] vss a[10] a[9] vdd a[8] a[7] vss a[6] a[5] vdd a[4] vss a[3] a[2] vdd a[1] a[0] vss vss dcs0 * ras1 * ras0 * cas3 * (cas0 * ) vdd cas2 * (cas1 * ) cas1 * (cas2 * ) cas0 * (cas3 * ) vss vdd dcke vss dclkin dclkout vdd dqmh (dqml) dqml (dqmh) 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 vdd io[1] vss vdat[3] vdat[2] vdat[1] vdat[0] vdd vss cp load df vss frame dispon vdd cpures * pon * onbutn nc pwrok pwrlnt pwrcs vss c32kout c32kln vdd bc32k vcc3 vss testaiu viddone testin testcpu vdd spiout spiin spiclk vss io[2] io[3] rxpwr cardet vdd vss irout irin nc io[4] txd rxd vdd 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 vdd d[18] (d[10]) vss d[19] (d[11]) d[20] (d[12]) vdd d[21] (d[13]) vss d[22] (d[14]) vddss d[23] (d[15]) d[24] (d[0]) vdd d[25] (d[1]) vss d[26] (d[2]) vss d[27] (d[3]) d[28] (d[4]) vdd d[29] (d[5]) vss d[30] (d[6]) d[31] (d[7]) vdd vss vss sysclkout sysclkin vdd cs1 * cs2 * cs3 * mcs0 * mcs1 * mcs2 * mcs3 * vss card1csh * card1csl * vdd carddir * vdd (pll) card1wait * cardreg * cardiowr * cardiord * vss (pll) io[0] card2csl * card2csh * card2wait * 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 vdd d[0] (d[24]) vss d[1] (d[25]) d[2] (d[26]) vdd d[3] (d[27]) vss d[4] (d[28]) vdd d[5] (d[29]) d[6] (d[30]) vss d[7] (d[31]) vss d[8] (d[16]) vdd d[9] (d[17]) d[10] (d[18]) vss d[11] (d[19]) vdd d[12] (d[20]) d[13] (d[21]) vss d[14] (d[22]) d[15] (d[23]) vdd endian miox[1] mbusint mbusdat a vss mbuscl k vdd vdd sibmcl k vss sibscl k sibsync sibdin sibdout vdd sibirq mio x [0] io[6] io[5] vss chicl k chifs chidin chidout www.datasheet.in chapter 2 pin descriptions 2-29 abc d e f g h j k l m n p r 1 3 d[1] ( d [ 25 ]) 1 vddh 2 d[0] ( d [ 24 ]) 5 d[3] ( d [ 27 ]) 9 d[5] ( d [ 29 ]) 13 d[9] ( d [ 17 ]) 17 d[12] ( d [ 20 ]) 21 vddh 28 vddh 33 sibsync 37 sibirq * 40 io[5] 43 chidin 44 chidout 47 io[4] 2 176 dqml ( dqmh ) 174 n.c. 4 d[2] ( d [ 26 ]) 10 d[6] ( d [ 30 ]) 12 d[8] ( d [ 16 ]) 16 d[11] ( d [ 19 ]) 22 endian 24 mbusint 26 vss 31 vss 35 sibdout 38 miox[0] 41 chiclk 42 chifs 45 rxd 3 175 dqmh ( dqml ) 172 dclkin 171 dcke 7 d[4] ( d [ 28 ]) 11 d[7] ( d [ 31 ]) 15 vss 20 d[15] ( d [ 23 ]) 18 d[13] ( d [ 21 ]) 27 mbusclk 30 sibmclk 34 sibdin 36 n.c. 39 io[6] 48 irin 46 txd 4 173 dclkout 170 vddh 168 cas1 * ( cas2 * ) 6 vss 8 vddl 14 d[10] ( d [ 18 ]) 19 d[14] ( d [ 22 ]) 23 miox[1] 25 mbusdata 29 vddl 32 sibsclk 50 vss 52 cardet 54 io[3] 49 irout 5 169 cas0 * ( cas3 * ) 167 cas2 * ( cas1 * ) 166 cas3 * ( cas0 * ) 164 ras1 * n.c. 51 vddl 55 io[2] 56 spiclk 53 rxpwr 6 165 ras0 * 163 dcs0 * 162 vss 161 a[0] 58 spiout 59 testcpu 60 testin 57 spiin 7 160 a[1] 158 a[2] 159 vddl 157 a[3] 63 vcc3 64 bc32k 66 c32kin 61 viddone 8 153 vss 156 a[4] 154 a[6] 155 a[5] bottom view 67 c32kout 62 testaiu 68 vss 65 vddh 9 149 a[9] 152 a[7] 151 a[8] 150 vddh 69 pwrcs 71 pwrok 70 pwrint 72 onbutn 10 145 we * 148 a[10] 147 a[11] 146 a[12] 75 vddl 73 pon* 74 cpures * 76 dispon 11 141 vddl 144 ale 143 dreq * 142 dgrnt * 77 frame 79 load 78 df 81 vss 12 137 vddh 140 vss 139 rd * 138 cs0 * 120 d[26] ( d [ 2 ]) 116 d[25] ( d [ 5 ]) 113 vddl 111 sysclkout 107 cs2 * 102 mcs3 * 98 vdd-pll 94 cardiord * 80 cp 82 vdat[0] 85 vdat[3] 13 134 vss 136 d[16] ( d [ 8 ]) 127 d[21] ( d [ 13 ]) 124 d[23] ( d [ 15 ]) 122 vddh 118 d[27] ( d [ 3 ]) 115 d[30] ( d [ 6 ]) 106 cs3 * 108 cs1 * 103 mcs2 * 99 carddir * 95 cardiowr * 83 vdat[1] 84 vdat[2] 87 io[1] 14 133 d[17] ( d [ 9 ]) 130 vss 128 d[20] ( d [ 12 ]) 126 vss 123 d[24] ( d [ 0 ]) 119 vss 114 d[31] ( d [ 7 ]) 112 vss 110 sysclkin 104 mcs1 * 100 card1csl * 96 cardreg * 92 io[0] 86 vss 88 vddh 15 135 n.c. 132 vddl 131 d[18] ( d [ 10 ]) 129 d[19] ( d [ 11 ]) 125 d[22] ( d [ 14 ]) 121 d[25] ( d [ 1 ]) 117 d[28] ( d [ 4 ]) 109 vddh 105 mcs0 * 101 card1csh * 97 card1wait * 93 vss-pll 90 card2csh * 89 card2wait * 91 card2csl * yy <- pin no. of qfp aaaa <- sin g al name on bi g endien mode ( bbbb ) <- signal name on little endien mode 2.4.6 TMPR3911bxb ball assignment p-fbga177-1313-0.80c4 ( ) should be used in little-endien mode. vddh: 3.3 v/vddl: 2.6 v www.datasheet.in chapter 2 pin descriptions 2-30 2.4.7 tmpr3912xb-92 p-fbga217-1313-0.80b6 r vdd io[4] irout rxpwr spiclk testcpu vss c32kin pwrint cpures * vss vss vdat[2] vdd card2wait * p chiout chidin nc vdd io[2] spiout testaiu c32kout pwrok vdd df vdd vdat[3] io[1] io[0] n vss chiclk rxd vss io[3] spiin viddone vdd nc dispon load vdat[0] card2csh * vss (pll) cardiowr * m sibirq miox[0] io[6] chicfs irin vss testin vss onbutn frame vdat[1] vss cardreg * card1wait * carddir * l sibsync sibdin sibdout io[5] txd cardet vdd bc32k pon * cp card2csl * cardiord * vdd card1csl * vss k vdd sibmclk vss sibsclk vdd nc vcc3 nc pwrcs nc vdd (pll) card1csh * mcs3 * mcs2 * mcs0 * j mbusint mbusdata vss mbusclk vdd miox[1] sysclkin mcs1 * cs3 * cs2 * cs1 * vdd h d[15] (d[23]) vdd d[14] (d[22]) endian nc vss bottom view nc sysclkout d[31] (d[7]) vss vdd vss g d[12] (d[20]) vdd d[11] (d[19]) vss d[9] (d[17]) d[13] (d[21]) nc d[30] (d[6]) d[27] (d[3]) d[28] (d[4]) vdd d[29] (d[5]) vss f d[10] (d[18]) vdd d[8] (d[16]) d[7] (d[31]) vdd nc a[2] nc a[6] nc vdd d[25] (d[1]) vss d[26] (d[2]) vss e vss vss d[6] (d[30]) vdd vss cas0 * (cas3 * ) vss a[5] a[10] dgrnt * d[16] (d[8]) vdd d[23] (d[15]) d[24] (d[0]) vdd d d[5] (d[29]) d[4] (d[28]) vss vdd vss cas3 * (cas0 * ) vss a[3] vdd vdd cs0 * vss d[21] (d[13]) vss d[22] (d[14]) c d[3] (d[27]) d[2] (d[25]) d[0] (d[24]) dcke cas1 * (cas2 * ) ras0 * a[0] vdd a[8] a[11] ale vss vss d[19] (d[11]) d[20] (d[12]) b d[1] (d[25]) dqmh (dqml) dclkout vdd cas2 * (cas1 * ) ras1 * a[1] vss a[7] vss we * vdd nc d[18] (d[10]) vdd a vdd dqml (dqmh) dclkin vss vdd dcs0 * vdd a[4] vss a[9] a[12] dreq * rd * vdd d[17] (d[9]) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ( ) should be used in little-endien mode. www.datasheet.in chapter 3 cpu module 3-1 3. cpu module 3.1 overview the TMPR3911/12 consists of an embedded tx39/h processor core along with the system interface logic required to support the pda system. these include a 4 kbyte instruction cache and a 1 kbyte data cache used to improve performance, a 32 32 multiplier with accumulator used to perform dsp functions to support features such as software modems. directly interfacing to the cpu core is the cpu interface logic. the cpu interface logic consists of a 4- deep write buffer used to speed up write transactions, dma arbitration logic used to arbitrate with the cpu core for siu dma requests and also used to provide cache coherency snooping during dma operations, and interface controller logic used to provide the necessary control to the cpu core and to provide a simple interface for initiating memory transactions to the biu. www.datasheet.in chapter 3 cpu module 3-2 3.2 cpu core 3.2.1 description there are several enhancements for the pda system. these additional key features of the cpu core are: ? translation look-aside buffer (tlb) (4 kbyte page size, 32 entries) ? 4 kbyte instruction cache (i-cache) ? 16 bytes (4 words) per line (256 lines total) ? physical address tag per cache line ? single valid bit per cache line ? programmable burst size (16 bytes to 128 bytes) ? instruction streaming mode supported ? direct-mapped ? 1 kbyte data cache (d-cache) ? 4 bytes (1 word) per line (128 lines total) ? physical address tag per cache line ? single valid bit per cache line ? programmable burst size (16 bytes to 128 bytes); burst refill can be disabled ? write-through ? two-way set associative ? cache address snoop mode supported for dma ? 32 32 on-chip hardware multiplier ? supports 32 32 (single-cycle) multiplier operations, with 64-bit accumulator ? signed or unsigned data formats ? accumulator supports sign-extension and overflow status ? existing multiply instructions are enhanced and new multiply and add instructions are added to the mips i instruction set to improve the performance of dsp applications www.datasheet.in chapter 3 cpu module 3-3 3.3 cpu interface 3.3.1 block diagram sdata from siu to test from test from test saddr taddr sack tack trd treq swrite sbyteen sstart sread sburst snoop dma grant write buffer full cpu byte enable dma request cpu write cpu data cpu address c p u r ead a c k c p u b us err o r cpu burst size c p u in st r uct i o n cpu burst ack burst from biu to b i u from biu to b i u datain byteen data addr halt buserror haltcycle halted wrinpage burstlen write read start c p u r ead interface controller write buffer dma arbiter tx39/h processor core to siu from siu figure 3.3.1 cpu interface block diagram the cpu interface logic consists of the interface controller, the write buffer and the dma arbiter. these blocks provide the cpu core with the interface to the biu to launch memory transactions as well as provide the siu with the interface to launch dma transactions to and from the biu. also provided is a test interface that allows reads and writes from and to internal function registers to bypass the cpu core. www.datasheet.in chapter 3 cpu module 3-4 3.3.2 write buffer the cpu core writes into the write buffer. the write buffer can store up to four write transactions and contains registers to buffer the address, data and byte enables. as long as there is space in the write buffer, the processor will not stall. once the write buffer is full, the cpu is stalled for subsequent writes until there is space in the write buffer. when the write buffer is not empty, the write buffer informs the interface controller to start a write transaction to the biu. once an acknowledge (ack) is received from the biu, the write buffer will proceed to the next address, data and byte enable in the buffer. a bus error from the biu will also cause the write buffer to proceed to the next address, data and byte enable. if the addresses of two consecutive writes are within a 512-byte page, the interface controller will assert the wrinpage signal. this signal allows the biu to keep the sdram and/or dram in page mode while writing within a 512-byte page. 3.3.3 interface controller the interface controller logic contains a state machine to control the interface between the cpu core and the biu. read transactions are initiated when the cpu core asserts the cpu read signal. write transactions are initiated whenever the write buffer is not empty. if the cpu attempts to start a read cycle while the write buffer is not empty, the write transaction will complete first and the remaining writes in the write buffer are flushed before allowing the read cycle to occur. the one exception is if the read is an instruction fetch from a cacheable location. in this case, the read will take place before the write buffer is flushed. if the interface controller is in the middle of an in page write (wrinpage asserted), then one more write transaction must occur to take the biu out of page mode before the read cycle can occur. the interface controller initiates a read or write to the biu by asserting the start signal. the read and write signals will indicate whether the biu should complete a read or write transaction. the cpu core will perform burst reads to fill the instruction and data caches. the cpu core can burst either 4, 8, 16 or 32 words depending on how the cpu core is configured. the state machine inside the interface controller will assert the burst signal to the biu and provide the burst size to the biu using the burstlen control signals. bursting can greatly enhance the memory bandwidth because the biu can keep the sdram and/or dram devices in page mode during a burst read. the biu will acknowledge that it is finished with a read or write by asserting the ack signal. the ack signal will also indicate that the data input datain is valid during a read. during a burst, there will be one ack for each word of data. if the address that is provided to the biu via the addr signals is not mapped into any physical space that is supported by the address decoder logic in the biu, the buserror signal will be asserted by the watch dog timer in the biu to terminate the bus cycle. the interface controller logic will use the buserror signal in place of the ack signal to end the bus cycle and proceed to the next transaction. if the buserror occurs on a processor read, the cpu bus error signal will be asserted to indicate to the cpu that a bus error has occurred. for writes the cpu bus error will not be asserted since the write would have long ago been completed into the write buffer and the bus error will not provide meaningful information. www.datasheet.in chapter 3 cpu module 3-5 the biu must halt the interface controller to prevent a bus cycle from starting in order to insert refresh, or when an external device requests the memory bus by asserting the dmareq* pin, or when the memory interface is powered down by asserting the mempowerdown control bit in the memory configuration 4 register. the biu will halt the interface controller by asserting the halt signal. the interface controller must then assert the halted signal once the state machine has completed the current memory transaction. once the biu sees the halted signal asserted, it can proceed to insert refresh or provide a dmagrnt* if an external device has requested the memory bus. once refresh is finished or the external device de-asserts the dmareq* signal, the biu will release the halt signal. if the halt signal is asserted due to the mempowerdown signal being set then the biu will not release the halt signal until the haltcycle signal is asserted by the interface controller. the haltcycle signal will be set whenever the interface controller starts a read or write cycle, but the halt signal is asserted. when the biu sees the haltcycle signal asserted, the biu will take one of two possible actions. on the one hand, if the address indicated by the addr signals corresponds to an internal function register, the biu will immediately de-assert the halt signal to allow the transaction to begin. once the start signal is asserted, the biu will immediately re-assert the halt signal to prevent subsequent memory transactions from beginning. on the other hand, if the address does not correspond to an internal function register, the biu must bring the memory interface out of power-down mode. this will take several cycles because the sdram and/or dram devices must be brought out of self refresh mode. once the memory interface is brought out of power-down mode, the biu will de-assert the halt signal. the action taken if the address is a function register allows the cpu core to access internal function registers without having to take the memory interface out of memory power-down mode. this is useful when the processor is running a program out of cache that only requires access to internal function registers. www.datasheet.in chapter 3 cpu module 3-6 3.3.4 dma arbitration the dma arbiter allows the siu to launch dma transactions to the biu. the siu will initiate a dma transaction by pulsing the sstart signal. once this occurs, the dma arbiter will assert the dma request signal to the cpu core. the cpu core will then assert the dma grant signal to indicate that the cpu is now idling. if the siu is performing a dma write (as indicated by the swrite signal), the saddr, sdata and sbyteen signals will then be loaded into the write buffer once there is space available in the write buffer. as soon as the write buffer loads the signals, the dma arbitration logic will assert the sack signal to indicate to the siu that the dma write is complete. at the same time that the data is loaded into the write buffer, the snoop signal is asserted to the cpu core. the snoop logic in the cpu core will invalidate the cache locations defined by the saddr bits when the snoop signal is asserted. this provides cache coherency during dma to simplify managing the cache. for a dma read transaction, the sread signal will be asserted by the siu. the write buffer will always be flushed before allowing the dma read to begin. once the write buffer is empty, the dma read will begin and the sack signal will be asserted to end the dma read once the biu asserts the ack signal. the siu will receive data input via the datain bus. the sburst signal from the siu is used to initiate burst reads. the siu will only request 4-word bursts, thus the burstlen signals will be set to a burst length of 4 whenever the sburst signal is asserted during dma reads. 3.3.5 cpu stop mode in order to reduce the power dissipation in the cpu core, the clock to the cpu core can be disabled. this is possible since the cpu core designs are implemented as fully static. the cpu core will normally be in stop mode and will only be active to process interrupts. the cpu enters to the cpu stop mode by setting the stopcpu control bit in the power control register. the stopcpu control bit will go to the dma arbitration logic, which will assert dma request to the cpu core upon the stopcpu signal being asserted. once the cpu core responds with a dma grant, the dma arbiter will assert a signal fstopcpu that is given to the clock generator to disable the clock to the cpu core. www.datasheet.in chapter 3 cpu module 3-7 3.3.6 tlb the tlb in the tx39/h core is based on r3000. the differences between the tlb in the tx39/h core and the tlb in the r3000 are as follows. (1) kseg2 tlb mapping area the address from 0xff00_0000 to 0xfffe_ffff in kseg2 is a reserved area. the following table shows the address mapping of the tx39/h core. segment virtual address physical address cacheable kseg2 0xffff_ffff 0xffff_0000 tlb mapped yes reserved 0xfffe_ffff 0xff00_0000 0xfffe_ffff 0xff00_0000 no kseg2 0xfeff_ffff 0xc000_0000 tlb mapped yes kseg1 0xbfff_ffff 0xa000_0000 0x1fff_ffff 0x0000_0000 no kseg0 0x9fff_ffff 0x8000_0000 0x1fff_ffff 0x0000_0000 yes kuseg 0x7fff_ffff 0xc000_0000 tlb mapped yes (2) multi-hit detection even though some of virtual address in the tlb entries are same, the tx39/h core does not detect multi-hit while the r3000 detects it. (3) the number of tlb entries the tx39/h core has 32 tlb entries while the r3000 has 64 tlb entries. 3.3.6.1 memory management system the tx39/h provides a full-featured memory management unit (mmu) utilizing an on-chip translation lookaside buffer (tlb) to provide very fast virtual memory accesses. this chapter describes the operation of the tlb and the cp0 registers that provide the software interface to the tlb. the memory mapping scheme supported by the tx39/h to translate virtual addresses to physical addresses is also described in detail. www.datasheet.in chapter 3 cpu module 3-8 3.3.6.2 memory system architecture the tx39/h?s virtual memory system logically expands the cpu?s physical memory space by translating addresses composed in a large virtual address space into the physical memory space of the tx39/h. figure 3.3.2 shows the form of an tx39/h virtual address. the most significant 20 bits of a 32- bit virtual address are called the virtual page number, or vpn. the vpn allows mapping of 4 kbyte pages, while the least significant 12 bits (the offset within a page) are passed along unchanged to form the physical address. the three most significant bits of vpn (bits 31..29) further define how addressed are mapped according to whether the tx39/h is in user mode or kernel mode (these modes are described in the paragraphs that follow). 0 x x kuseg 1 0 0 kseg0 1 0 1 kseg1 1 1 x kseg2 offset vpn 12 20 29 30 31 0 11 12 31 figure 3.3.2 virtual address format a 6-bit process identifier field is appended to each virtual address to form unique virtual addresses for up to 64 processes. the mapping of these extended, process-unique virtual addresses to physical addresses need not be one-to-one; virtual addresses of two or more different processes may map to the same physical address. www.datasheet.in chapter 3 cpu module 3-9 3.3.6.3 privilege states the tx39/h provides two privilege states: the kernel mode, which is analogous to the ?supervisory? mode provided by many machines, and the user mode, where non-supervisory programs are executed. the tx39/h enters the kernel mode whenever an exception is detected and remains in the kernel mode until a restore from exception ( rfe ) instruction is executed. address mapping is different for kernel and user modes. to simplify the management of user state from within the kernel, the user-mode address space is a subset of the kernel-mode address space. figure 3.3.3 shows the virtual-to-physical memory map for both the user mode and kernel mode segments. c000 0000 kernel mapped cacheable kseg2 ffff ffff ffff ffff 2048 mbytes (tlb) 512 mbytes 512 mbytes 512 mbytes 1024 mbytes (tlb) physical virtual a000 0000 kernel unmapped uncached kseg1 bfff ffff 8000 0000 kernel unmapped cached kseg0 9fff ffff 000 0000 user mapped cacheable kuseg 7fff ffff 2000 0000 0000 0000 1fff ffff 3684 mbytes any any ffff 0000 reserved feff ffff ffff 0000 reserved feff ffff figure 3.3.3 the tx39/h virtual memory map www.datasheet.in chapter 3 cpu module 3-10 3.3.6.4 user-mode virtual addressing when the processor is operating in user mode, a single, uniform virtual address space (kuseg) of 2 gbytes is available for users. all valid user-mode virtual addresses have the most-significant bit cleared to 0. an attempt to reference an address with the most-significant bit set while in the user mode causes an address error exception. the 2 gbyte user segment begins at address zero. the tlb maps all references to kuseg identically from kernel and user modes and controls access cacheability. (the n bit in a tlb entry determines whether the reference will be cached.) kuseg is typically used to hold user code and data, and the current user process typically resides in kuseg. 3.3.6.5 kernel-mode virtual addressing when the processor is operating in kernel mode, three distinct virtual address spaces (in addition to kuseg) are simultaneously available. the three segments dedicated to the kernel are: ? kseg0. this cached, unmapped segment begins at virtual address 0x8000_0000 and is 512 mbytes long. ? kseg1. this uncached, unmapped segment begins at virtual address 0xa000_0000 and is 512 mbytes long. ? kseg2. this kernel-mapped, cacheable segment begins at virtual address 0xc000_0000 and is 1 gbytes long. kseg0. when the most-significant three bits of the virtual address are ?100?, the virtual address space selected is a 512-mbyte kernel physical space (kseg0). the tx39/h direct-maps references within kseg0 onto the first 512 mbytes of physical address space. these references use cache memory, but they do not use tlb entries. thus, kseg0 is typically used for kernel executable code and some kernel data. kseg1. when the most-significant three bits of the virtual address are ?101?, the virtual address space selected is a 512-mbyte kernel physical space (kseg1). the processor directly maps kseg1 onto the first 512 mbytes of physical address space and uses no tlb entries. unlike kseg0, kseg1 uses uncashed references. an operating system typically uses kseg1 for i/o register, rom code, and disk buffers. kseg2. when the most-significant two bits of the virtual address are ?11?, the virtual address space selected is a 1024 mbyte kernel virtual space (kseg2). like kuseg, kseg2 uses tlb entries to map virtual addresses to arbitrary physical ones, with or without caching. (the n bit in a tlb entry determines whether the reference will be cached.) an operating system typically uses kseg2 for stacks and per-process data that it must remap on context switches, for user page tables (memory map), and for some dynamically allocated data areas. kseg2 allows selective caching and mapping on a per-page basis, rather than requiring an all or nothing approach. www.datasheet.in chapter 3 cpu module 3-11 3.3.6.6 virtual memory and the tlb mapped virtual addresses are translated into physical addresses using a translation lookaside buffer (tlb). the tlb is a fully associative memory device that holds 32 entries to provide mapping of 32 4 kbyte pages. when address mapping is indicated (that is, when the access is in kuseg or kseg2 ), each tlb entry is simultaneously checked for a match with the extended virtual address. the cpu supports up to four coprocessors. coprocessor 0 (cp0), which is called the system control coprocessor, is implemented as an integral part of the tx39/h. cp0 supports address translation, exception handling, and other ?privileged? operations. it consists of the 32-entry tlb plus the ten registers shown in figure 3.3.4. the sections that follow describe how each of the four tlb-related registers is used. (note: cp0 functions and registers associated with exception handling are described in chapter 6 of the 32-bit tx system risc tx39 family architecture manual.) cp0 & the tlb prld badva epc register cause register context register status register random register index register (?safe? entries) (see random register) 7 0 8 31 tlb entrylo register entryhi register config re g ister figure 3.3.4 the cp0 registers & the tlb 3.3.6.7 tlb entries each tlb entry is 32 bits wide and its format is shown in figure 3.3.5 each of the fields of a tlb entry has a corresponding field in the entryhi/entrylo register pair described next. refer to figure 3.3.6 for a description of each of the tlb entry fields. ndvg 0 0 63 pfn pid 0 vpn 6 20 6 20 1 1 1 1 8 figure 3.3.5 format of a tlb entry www.datasheet.in chapter 3 cpu module 3-12 3.3.6.8 entryhi & entrylo registers (cp0 register no.10, no.2) these two registers provide the data pathway through which the tlb is read, written, or probed. when address translation exceptions occur, these registers are loaded with relevant information about the address that caused the exception. the format of the entryhi and entrylo register pair a is the same as the format of tlb entry and is illustrated in figure 3.3.6. entrylo is the natural form of a page table entry (pte); however, since ptes are always loaded by system software, not by the tx39/h hardware, an operating system can use another format for memory-resident ptes. tlb entryhi register (cp0 register no.10) 32 37 38 43 44 63 pid 0 vpn 6 20 6 vpn virtual page number. bits 31..12 of virtual address. pid process id process id field. a 6-bit field which lets multiple processes share the tlb while each process has a distinct mapping of otherwise identical virtual page numbers. 0 reserved. currently ignores writes, returns zero when read. tlb entrylo register (cp0 register no.2) 0 7 8 9 10 11 12 31 g pfn 20 1 0 8 v 1 d 1 n 1 pfn page frame number. bits 31..12 of the physical address. the tx39/h maps a virtual page to pfn. n non-cacheable. if this bit is set, the page is marked as non-cacheable and the tx39/h directly accesses main memory instead of first accessing the cache. d dirty. if this bit is set, the page is marked as ?dirty? and therefore writable. this bit is actually a ?write- protect? bit that software can use to prevent alteration of data. if an entry is accessed for a write operation when the d bit is cleared, the tx39/h causes a tlb mod trap. the tlb entry is not modified on such a trap. v valid. if this bit it set, it indicates that the tlb entry is valid; otherwise, a tlbl or tlbs miss occurs. g global. if this bit it set, the tx39/h ignores the pid match requirement for valid translation. in kseg2, the global bit lets the kernel access all mapped data without requiring it to save or restore pid (process id) values. 0 reserved. currently ignores writes, returns zero when read. figure 3.3.6 the tlb entryhi & entrylo registers www.datasheet.in chapter 3 cpu module 3-13 3.3.6.9 virtual address translation during virtual-to-physical address translation, the tx39/h compares pid and the highest 20 bits (the vpn) of the virtual address to the contents of the tlb. figure 3.3.7 illustrates the tlb address translation process. a virtual address matches a tlb entry when the virtual page number (vpn) field of the virtual address equals the vpn field of the entry, and either the global (g) bit of the tlb entry is set, or the process identifier (pid) field of the virtual address (as held in the entryhi register) matches the pid field of the tlb entry. while the valid (v) bit of the entry must be set for a valid translation to take place, it is not involved in the determination of a matching tlb entry. if a tlb entry matches, the physical address and access control bits (n, d, and v) are retrieved from the matching tlb entry. otherwise, a tlb miss (or utlb miss) exception occurs. if the access control bits (d and v) indicate that the access is not valid, a tlb modification or tlb miss exception occurs. if the n bit is set, the physical address that is retrieved is used to access main memory, bypassing the cache. www.datasheet.in chapter 3 cpu module 3-14 no yes dirty yes yes no no yes non- cacheable exception tlb mod access main memory access cache output physical address exception exception utlb miss tlb miss msb = 1 n = 1 write d = 1 v = 1 g = 1 pid match vpn match msb = 1 user mode address error vpn & pid input virtual address address translation no no no no no no yes yes yes yes global valid yes yes figure 3.3.7 tlb address translation www.datasheet.in chapter 3 cpu module 3-15 3.3.6.10 the index register (cp0 register no.0) the index register is a 32-bit, read/write register, which has 5 bits that index an entry in the tlb. the most significant bit of the register shows the success or failure of a tlb probe (tlbp) instruction (described later in this chapter). the index register also specifies the tlb entry that will be affected by the tlb read (tlbr) and tlb write index (tlbwi) instructions. figure 3.3.8 shows the format of the index register. index register 0 7 8 12 13 30 31 index 0 0 5 17 8 p 1 p probe failure. set to 1 when the last tlbprobe (tlbp) instruction was unsuccessful. index index to the tlb entry that will be affected by the tlbread and tlbwrite instruction. 0 reserved. currently ignores writes, returns zero when read. figure 3.3.8 the index register 3.3.6.11 the random register (cp0 register no.1) the random register is a 32-bit register. the format of the random register is shown in figure 3.3.9. the five-bit random filed indexes a random entry in the tlb. the tx39/h decrements the random field during every machine cycle but constrains the value of this field to the tlb indexes from 31 to 8 (the counter wraps around from 8 to 31 skipping values 7 through 0). the tlb write random (tlbwr) instruction is used to write the tlb entry that this register indexes. the first eight entries (0 to 7) are the ?safe? entries because a tlbwr instruction can never replace the contents of these entries. typically, these eight entries are reserved for use by the operating system. although normal operations never require it, the contents of this register can be read to verify proper operation of the process. to further simplify testing, the random field is set to a value of 31 when the tx39/h is reset. random register 0 7 8 12 13 31 random 0 0 5 18 8 random a random index with a value ranging from 8 to 31 to a tlb entry. 0 reserved. currently ignores writes, returns zero when read. figure 3.3.9 the random register www.datasheet.in chapter 3 cpu module 3-16 3.3.6.12 tlb instructions the instructions that the tx39/h provides for working with the tlb are listed in table 3.3.1 and described briefly below. table 3.3.1 tlb instructions op code description tlbp translation lookaside buffer probe tlbr translation lookaside buffer read tlbwi translation lookaside buffer write index tlbwr translation lookaside buffer write random translation lookaside buffer probe (tlbp). this instruction probes the tlb to see if an entry matches the entryhi register contents. if a match exists, the tx39/h loads the index register with the index of the entry that matches the entryhi register. when on match exists, the tx39/h sets the high order bit (the p bit) of the index register. translation lookaside buffer read (tlbr). this instruction loads entryhi and entrylo registers with the contents of the tlb entry specified by the contents of the index register. translation lookaside buffer write index (tlbwi). this instruction loads specified tlb entry with the contents of the entryhi and entrylo registers. the contents of the index register specify the tlb entry. translation lookaside buffer write random (tlbwr). this instruction loads a pseudo-randomly specified tlb entry with the contents of the entryhi and entrylo registers. the contents of the random register specify the tlb entry. www.datasheet.in chapter 4 biu module 4-1 4. biu module 4.1 overview the biu provides an interface to the memory devices in the system, including static devices, as well as dram, hdram and sdram devices. an overall block diagram of the biu is shown in figure 4.1.1. the biu provides control to support the following memory devices: ? sdram chip select (dcs0*, dcs1*) and/or dram (ras0*, ras1*) ? 8-bit or 16-bit data bus width sdram configuration ? 16-bit or 32-bit data bus width dram configuration ? 16-bit or 32-bit data bus width hdram configuration ? 4 mbit, 16 mbit, 64 mbit and 128 mbit (*) parts supported (*) 128 mbit is supported only by tmpr3912au-92/xb-92. ? page mode reads and writes supported ? independent refresh counters for each bank ? self refreshing parts supported to retain memory when system is powered down ? 4 general purpose chip selects (cs3*-cs0*) ? 16-bit or 32-bit ports ? programmable wait states ? read page mode ? 4 general purpose chip selects (mcs3*- mcs0*) ? 16-bit ports ? programmable wait states ? read page mode ? 2 full pcmcia slots ? 8 bit or 16 bit ports ? iord and iowr provided to support i/o cards ? wait signal supported most of the biu logic uses the clk signal ( 4 frequency of sysclk) as the clock, but in order to increase the memory bandwidth, sdram devices are accessed using the signal dclkout ( 8 frequency of sysclk). the dclkout signal is also used to provide more precise timing for generating the control signals for the chip selects, as well as the sdram and dram control signals. input data is sampled using the dclkin signal which is connected externally to the dclkout signal. the external connection ensures that the input data and dclkin will not be skewed, which is necessary to meet the hold time specification on the sdram devices. also, the external looping of dclkout to dclkin helps to improve the access time of normal drams, since the input data will be sampled closer to the end of the access. www.datasheet.in chapter 4 biu module 4-2 4.1.1 block diagram output data ack dram control sdram control addr[31:0] byteen halted haltcycle halt buserror cs3-cs0 mcs3-mcs0 card control start read write burst burstlen wrinpage a[12:0] d[31:0] input data memory state machine chip select controller address decoder arbitrator output data path input data path dram & sdram controller figure 4.1.1 biu block diagram www.datasheet.in chapter 4 biu module 4-3 4.2 address decoder the address decoder provides the decoding for the address space in the system. the address decoder also contains the logic to generate the address signals a[12:0] for the memory devices, along with address re-mapper logic used to re-direct memory addresses. 4.2.1 system address map the system address map is shown in table 4.2.1. the address space is partitioned to support two banks (bank 1 and bank 0) of dram and/or sdram, four general purpose 16/32-bit chip selects (cs3-cs0), four general purpose 16-bit-only chip selects (mcs3-mcs0), two pcmcia slots (card 2 and card 1), and internal function register access. the address space contains two primary regions: kseg0/kseg1 are only accessible in kernel mode, while kuseg is accessible in either user or kernel mode. mcs3-mcs0 are available in kuseg space and are thus always available to either user or kernel mode accesses. cs3-cs1 are located in both kseg and kuseg space, but accesses in kuseg space can be independently disabled for each chip select using the encs3user, encs2user, and encs1user control bits in the memory configuration 0 register. cs0 is used as the chip select for the boot rom in the system. it is mapped starting at address $11000000 in kernel space, which will map into the tx39/h boot vector location at address $1fc00000. cs0 is also mapped in kuseg space to allow access to the rom by programs operating in user mode. card 1 and card 2 are mapped into kuseg space for memory accesses and kernel-only space for io and attribute accesses. to access the attribute space in a card, the card1ioen or card2ioen bits in the memory configuration 3 register must be cleared prior to accessing the card space. for i/o accesses the card1ioen or card2ioen bits must be set prior to accessing the card space. the processor can write to the mode registers in the sdrams in kernel mode at address $10e00000 and $10f00000 for bank 0 and bank 1 sdram banks, respectively. bank 0 and bank 1 are each mapped into four different locations. each location is just an image of the other locations. each bank can contain either dram or sdram devices, with the only restriction being that bank 1 cannot contain sdram if bank 0 contains dram. a system can be built without dram or sdram and instead can contain sram as the main memory. in this case at least one bank of sram should be connected to cs1 and the encs1dram control bit in the memory configuration 0 register should be set. setting this bit will cause cs1 to map in place of bank 0 and bank 1, as shown in table 4.2.1. this is required because exception vectors are mapped into physical address 0x0000_0080 (in case of beu = 0 in tx39/h core status register), thus it is required that some memory exist in this region to support exception handling. accesses to reserved or non-enabled locations will respond with a bus error if the watch dog timer is enabled. www.datasheet.in chapter 4 biu module 4-4 table 4.2.1 system address map (physical address) size address segment devices 16 mbyte ff00_0000 reserved reserved 1 gbyte c000_0000 kseg2 reserved 1 gbyte 7c00_0000 kuseg reserved 64 mbyte 7800_0000 kuseg mcs3 64 mbyte 7400_0000 kuseg mcs2 64 mbyte 7000_0000 kuseg mcs1 64 mbyte 6c00_0000 kuseg mcs0 64 mbyte 6800_0000 kuseg card 2 (memory) 64 mbyte 6400_0000 kuseg card 1 (memory) 64 mbyte 6000_0000 kuseg cs3 (if enabled) 64 mbyte 5c00_0000 kuseg cs2 (if enabled) 64 mbyte 5800_0000 kuseg cs1 (if enabled) 128 mbyte ( * ) 5000_0000 kuseg cs0 (rom) 128 mbyte 4800_0000 kuseg reserved 32 mbyte 4600_0000 kuseg dram bank1 32 mbyte 4400_0000 kuseg dram bank0 32 mbyte 4200_0000 kuseg cs1 (if enabled, else dram bank 1) 32 mbyte 4000_0000 kuseg cs1 (if enabled, else dram bank 0) 512 mbyte 2000_0000 reserved reserved 240 mbyte ( * ) 1100_0000 kseg0, kseg1 cs0 (rom) 1 mbyte 10f0_0000 kseg0, kseg1 sdram bank 1 mode register 1 mbyte 10e0_0000 kseg0, kseg1 sdram bank 0 mode register 2 mbyte 10c0_0000 kseg0, kseg1 internal function registers 4 mbyte 1080_0000 kseg0, kseg1 cs3 4 mbyte 1040_0000 kseg0, kseg1 cs2 4 mbyte 1000_0000 kseg0, kseg1 cs1 64 mbyte 0c00_0000 kseg0, kseg1 card 2 (i/o or attribute) 64 mbyte 0800_0000 kseg0, kseg1 card 1 (i/o or attribute) 32 mbyte 0600_0000 kseg0, kseg1 dram bank1 32 mbyte 0400_0000 kseg0, kseg1 dram bank 0 32 mbyte 0200_0000 kseg0, kseg1 cs1 (if enabled, else dram bank 1) 32 mbyte 0000_0000 kseg0, kseg1 cs1 (if enabled, else dram bank 0) ( * ) note: since external addresses (ha[25:0] are only 26 bit width, memory space which can be used physically is only 64 mbyte of these cs0 area. upper 5 bits of internal addresses (addr[31:27]) are discarded, so the access to the remaining area overlaps to the physical 64 mbyte area. www.datasheet.in chapter 4 biu module 4-5 4.2.2 address generation the address decoder logic generates the a[12:0] address bus for the memory devices. addresses are multiplexed on the a[12:0] address bus. for static devices such as cs3-cs0, mcs3-mcs0, card 2 and card 1, the addresses are multiplexed such that addr[25:13] is provided first-in-time followed by addr[12:0], as shown in figure 4.2.1. addr[25:13] must be latched with an external latch using the ale signal. the latched addresses concatenated with a[12:0] will provide a 26-bit address bus for the system, ha[25:0]. ha[25:0] a[12:0] ale addr[25:13] addr[12:0] tx3911/12 ale a[12:0] q d le ha[25:0] figure 4.2.1 ale timing dram and sdram devices contain multiplexed address buses. thus, a[12:0] will be directly connected to the dram and sdram devices. in order to support a wide range of dram and sdram types and configurations, there are control bits in the memory configuration 0 register that provide software configuration for the row and column address bit positions. these control bits are rowsel0[1:0] and colsel0[2:0] for bank 0, and rowsel1[1:0] and colsel1[2:0] for bank 1. table 4.2.2 shows the position that specific address bits are placed, depending on the configuration of the control bits. this flexibility in address bit positioning makes it possible to support 4-mbit, 16-mbit, and 64-mbit dram and sdram devices with different bus width configurations. the two sets of control bits make it possible to support different devices in bank 0 and bank 1. the ? ? character in the table means that this bit position will be a zero and the ?x? implies a ?don?t care? bit position. table 4.2.2 tmpr3912 dram and sdram address mapping row a[12:0] rowsel col a[12:0] colsel 18, 17:9 00 22, 20, 18, 8:1 0000 22, 18, 20, 19, 17:9 01 19, 18, 8:2 0001 20, 22, 21, 19, 17:9 10 21, 20, 18, 8:2 0010 22, 23, 21, 19, 17:9 11 23, 22, 20, 18, 8:2 0011 24, 22, 20, 18, 8:2 0100 18, , x, 8:0 0101 22, x, , 21, 8:0 0110 18, , x, 21, 8:1 0111 22, x, , 23, 21, 8:1 1000 24, 23, 21, 8:2 1001 example: when rowsel[1:0] = 01, the address bits addr[22], addr[18], addr[20], addr[19] and addr[17:9] are outputed to a[12], a[11], a[10], a[9] and a[8:0] pins respectively as row address for dram and/or sdram. when colsel[3:0] = 1000, the address bits addr[22], undefined value, zero data, addr[23], addr[21], and addr[8:1] are outputed to a[12], a[11], a[10], a[9], a[8], a[7:0] respectively as column address for dram and/or sdram. www.datasheet.in chapter 4 biu module 4-6 4.2.3 address re-mapper logic the address decoder logic provides an address re-mapper that allows addresses to be re-directed. there are two separate sets of re-mapper registers provided. the memory configuration 5-8 registers contain the startval2[31:9], mask2[3:0] and rmapadd2[31:9] control bits for one re-mapper, and the startval1[31:9], mask1[3:0] and rmapadd1[31:9] control bits for the other re-mapper. each re-mapper contains its own enable bit defined by the enrmap2 and enrmap1 control bits in the memory configuration 0 register. if the enable bits are not set, then no address re-mapping will occur. the re-mapper works as described in the following paragraph. the addr[31:2] address output of the cpu interface is compared with the startval[31:9] bits. if the addresses compare, the upper address bits are replaced with the rmapadd[31:9] bits. the lower bits[8:2] are always passed through. this provides a 512-byte block that can be re-mapped to any other 512-byte block. the mask[3:0] bits are used to select either a 512, 1k, 2k, 4k or 8 kbyte block. a bitwise ?and? of the mask[3:0] bits with addr[12:9] is performed before the address comparison. if the address compares to the startval bits then the address is replaced with the rmapadd bits. the resulting address is then provided to the address decoder logic. table 4.2.3 shows the resulting address when the comparison is true for the different possible mask settings. the startval[12:9] bits are valid as shown by the ?v? in the table. otherwise the bits must be set to zero as shown. table 4.2.3 address re-mapper mask[3:0] startval[12:9] address result f v, v, v, v rmapadd[31:9], addr[8:2] e v, v, v, 0 rmapadd[31:10], addr[9:2] c v, v, 0, 0 rmapadd[31:11], addr[10:2] 8 v, 0, 0, 0 rmapadd[31:12], addr[11:2] 0 0, 0, 0, 0 rmapadd[31:13], addr[12:2] the primary function of the re-mapper logic is to support flash devices, which have slow write access times, are block-oriented, and require a lot of overhead. the re-mapping of flash writes into normal memory space allows the flash to be written much less frequently. anytime a write occurs within the re-mapped range, the write will instead take place into the desired re-mapped memory location. the software can then setup memory protection to protect writes to the rest of the flash, outside of the previously selected range or block. once a memory protection exception occurs, the software can disable the re-mapper, move the data from normal memory to the flash, then move the startval bits to point to a new address, corresponding to a new address block. www.datasheet.in chapter 4 biu module 4-7 4.3 chip select controller 4.3.1 description the chip select controller provides the logic required to generate cs3-cs0, mcs3-mcs0, card 2, and card 1 control signals. cs3-cs0 can each independently be set as either 32-bit or 16-bit ports. mcs3-mcs0, are always 16-bit ports. card 2 and card 1 can be set as either 16-bit or 8-bit ports. the access time for each chip select is individually programmed using the control bits in the memory configuration 1-3 registers. also provided for cs3-cs0 and mcs3-mcs0 is separate access time control for read page mode that can be enabled or disabled independently for each chip select using the encs page ( = 0, 1, 2, 3), enmcs page ( = 0, 1, 2, 3) control bits in the memory configuration 3 register. the read page mode provides burst read capability to support memory devices such as page mode roms. there is separate access time control provided for memory accesses to card 2 or card 1, or io/attribute accesses to card 2 or card 1. the address inputs for all 32-bit memory devices should be connected starting with ha[2] and all 16-bit memory devices should be connected starting with ha[1]. the pcmcia cards will use all the address bits ha[25:0]. www.datasheet.in chapter 4 biu module 4-8 4.3.2 access mapping this section describes the mapping between the byte lanes of the cpu registers (r[ ]) and the byte lanes of external signals (d[ ]). depending upon cpu endianness, the signal names of some pins are reorganized (see table 4.3.1). in this section xl[ ] means x[ ] in little-endian mode, xb[ ] means x[ ] in big-endian mode. for example casl[ ] means cas[ ] in little-endian mode, and casb[ ] means cas[ ] in big-endian mode. example: in case of little-endian, the physical pins [133:145] are named dl[7:0], whereas in big-endian case, the same physical pins are named db[31:24]. table 4.3.1 signal name in each endian mode pin no. 3911bxb 3912au-92 3912xb-92 little-endian big-endian p7, n7, m6, r7, n6, m5, r6, p5 133-145 h12-e14 dl[7:0] db[31:24] n4, r5, n3, p3, r4, r3, p1, n2 146-159 e13-e11 dl[15:8] db[23:16] c7, d7, c8, a7, b6, d6, a6, b5 27-16 h1-f3 dl[23:16] db[15:8] c5, b4, a5, c4, a4, b3, a1, a3 14-2 f4-c3 dl[31:24] db[7:0] e3 195 d6 casl[0] * casb[3] * e2 197 b5 casl[1] * casb[2] * d3 198 c5 casl[2] * casb[1] * e1 199 e6 casl[3] * casb[0] * c1 207 b2 dqmll dqmhb b1 208 a2 dqmhl dqmlb p11 117 l14 card1csl * card1csl * ( * 1) r10 118 k12 card1csh * card1csh * ( * 1) r15 107 l11 card2csl * card2csl * ( * 1) r13 106 n13 card2csh * card2csh * ( * 1) * 1) not affected by endianness table 4.3.2, 4.3.3, 4.3.4, and 4.3.5 show the access mapping in little-endian mode, and table 4.3.6, 4.3.7, 4.3.8, and 4.3.9 shows the access mapping in big-endian mode. note that in both little-endian configuration and big-endian configuration, each device is connected to the same physical pins. www.datasheet.in chapter 4 biu module 4-9 table 4.3.2 access mapping (sdram in little-endian mode) (x: undefined) access ha[1:0] data bus width ( * 1) dqmhl, dqmll dl[31:24] dl[23:16] dl[15:8] dl[7:0] word(1/2) 00 16-bit ll r[15:8] r[7:0] x x word(2/2) 10 16-bit ll r[31:24] r[23:16] x x triple byte(1/2) 01 16-bit lh r[15:8] x x x triple byte(2/2) 10 16-bit ll r[31:24] r[23:16] x x triple byte(1/2) 00 16-bit ll r[15:8] r[7:0] x x triple byte(2/2) 10 16-bit hl x r[23:16] x x half-word 00 16-bit ll r[15:8] r[7:0] x x half-word 10 16-bit ll r[15:8] r[7:0] x x byte 00 16-bit hl x r[7:0] x x byte 01 16-bit lh r[7:0] x x x byte 10 16-bit hl x r[7:0] x x byte 11 16-bit lh r[7:0] x x x word(1/4) 00 8-bit lh r[7:0] x x x word(2/4) 01 8-bit lh r[15:8] x x x word(3/4) 10 8-bit lh r[23:16] x x x word(4/4) 00 8-bit lh r[31:24] x x x triple byte(1/3) 01 8-bit lh r[15:7] x x x triple byte(2/3) 10 8-bit lh r[23:16] x x x triple byte(3/3) 11 8-bit lh r[31:24] x x x triple byte(1/3) 00 8-bit lh r[7:0] x x x triple byte(2/3) 01 8-bit lh r[15:8] x x x triple byte(3/3) 10 8-bit lh r[23:16] x x x half-word(1/2) 00 8-bit lh r[7:0] x x x half-word(2/2) 01 8-bit lh r[15:8] x x x half-word(1/2) 10 8-bit lh r[7:0] x x x half-word(2/2) 11 8-bit lh r[15:8] x x x byte 00 8-bit lh r[7:0] x x x byte 01 8-bit lh r[7:0] x x x byte 10 8-bit lh r[7:0] x x x byte 11 8-bit lh r[7:0] x x x * 1) selected by memory configuration 0 register bank conf[1:0] ( = 0, 1). www.datasheet.in chapter 4 biu module 4-10 table 4.3.3 access mapping (dram/hdram in little-endian mode) access ha[1:0] data bus width ( * 1) casl[3:0] * ( * 2) dl[31:24] dl[23:16] dl[15:8] dl[7:0] word 00 32-bit llll r[31:24] r[23:16] r[15:8] r[7:0] triple byte 00 32-bit hlll x r[23:16] r[15:8] r[7:0] triple byte 01 32-bit lllh r[31:24] r[23:16] r[15:8] x half-word 00 32-bit hhll x x r[15:8] r[7:0] half-word 10 32-bit llhh r[15:8] r[7:0] x x byte 00 32-bit hhhl x x x r[7:0] byte 01 32-bit hhlh x x r[7:0] x byte 10 32-bit hlhh x r[7:0] x x byte 11 32-bit lhhh r[7:0] x x x word(1/2) 00 16-bit llhh r[15:8] r[7:0] x x word(2/2) 10 16-bit llhh r[31:24] r[23:16] x x triple byte(1/2) 01 16-bit lhhh r[15:8] x x x triple byte(2/2) 10 16-bit llhh r[31:24] r[23:16] x x triple byte(1/2) 00 16-bit llhh r[15:8] r[7:0] x x triple byte(2/2) 10 16-bit hlhh x r[23:16] x x half-word 00 16-bit llhh r[15:8] r[7:0] x x half-word 10 16-bit llhh r[15:8] r[7:0] x x byte 00 16-bit hlhh x r[7:0] x x byte 01 16-bit lhhh r[7:0] x x x byte 10 16-bit hlhh x r[7:0] x x byte 11 16-bit lhhh r[7:0] x x x * 1) selected by memory configuration 0 register bank conf[1:0] ( = 0, 1). * 2) asserted for both read access and write access. www.datasheet.in chapter 4 biu module 4-11 table 4.3.4 access mapping (cs and mcs in little-endian mode) (x: undefined) access ha[1:0] port size ( * 1) casl[3:0] * ( * 2) dl[31:24] dl[23:16] dl[15:8] dl[7:0] word 00 32-bit llll r[31:24] r[23:16] r[15:8] r[7:0] triple byte 00 32-bit hlll x r[23:16] r[15:8] r[7:0] triple byte 01 32-bit lllh r[31:24] r[23:16] r[15:8] x half-word 00 32-bit hhll x x r[15:8] r[7:0] half-word 10 32-bit llhh r[15:8] r[7:0] x x byte 00 32-bit hhhl x x x r[7:0] byte 01 32-bit hhlh x x r[7:0] x byte 10 32-bit hlhh x r[7:0] x x byte 11 32-bit lhhh r[7:0] x x x word(1/2) 00 16-bit hhll x x r[15:8] r[7:0] word(2/2) 10 16-bit hhll x x r[31:24] r[23:16] triple byte(1/2) 01 16-bit hhlh x x r[15:8] x triple byte(2/2) 10 16-bit hhll x x r[31:24] r[23:16] triple byte(1/2) 00 16-bit hhll x x r[15:8] r[7:0] triple byte(2/2) 10 16-bit hhhl x x x r[23:16] half-word 00 16-bit hhll x x r[15:8] r[7:0] half-word 10 16-bit hhll x x r[15:8] r[7:0] byte 00 16-bit hhhl x x x r[7:0] byte 01 16-bit hhlh x x r[7:0] x byte 10 16-bit hhhl x x x r[7:0] byte 11 16-bit hhlh x x r[7:0] x * 1) selected by memory configuration 0 register cs size (cs * ) ( = 0, 1, 2, 3). port size for mcs * ( = 0, 1, 2, 3) are fixed to 16 bit width. * 2) asserted for write access only. www.datasheet.in chapter 4 biu module 4-12 table 4.3.5 access mapping (pcmcia in little-endian mode) (x: undefined) access ha[1:0] port size ( * 1) cardcsnh * , cardcsnl * dl[31:24] dl[23:16] dl[15:8] dl[7:0] word(1/2) 00 16-bit ll x x r[15:8] r[7:0] word(2/2) 10 16-bit ll x x r[31:24] r[23:16] triple byte(1/2) 01 16-bit lh x x r[15:8] x triple byte(2/2) 10 16-bit ll x x r[31:24] r[23:16] triple byte(1/2) 00 16-bit ll x x r[15:8] r[7:0] triple byte(2/2) 10 16-bit hl x x x r[23:16] half-word 00 16-bit ll x x r[15:8] r[7:0] half-word 10 16-bit ll x x r[15:8] r[7:0] byte 00 16-bit hl x x x r[7:0] byte 01 16-bit lh x x r[7:0] x byte 10 16-bit hl x x x r[7:0] byte 11 16-bit lh x x r[7:0] x word(1/2) 00 8-bit ll x x r[15:8] r[7:0] word(2/2) 10 8-bit ll x x r[31:24] r[23:16] triple byte(1/2) 01 8-bit hl x x x r[15:8] triple byte(2/2) 10 8-bit ll x x r[31:24] r[23:16] triple byte(1/2) 00 8-bit ll x x r[15:8] r[7:0] triple byte(2/2) 10 8-bit hl x x x r[23:16] half-word 00 8-bit ll x x r[15:8] r[7:0] half-word 10 8-bit ll x x r[15:8] r[7:0] byte 00 8-bit hl x x x r[7:0] byte 01 8-bit hl x x x r[7:0] byte 10 8-bit hl x x x r[7:0] byte 11 8-bit hl x x x r[7:0] * 1) selected by memory configuration 3 register port8sel www.datasheet.in chapter 4 biu module 4-13 table 4.3.6 access mapping (sdram in big-endian mode) access ha[1:0] data bus width ( * 1) dqmhb, dqmlb db[31:24] db[23:16] db[15:8] db[7:0] word(1/2) 00 16-bit ll x x r[31:24] r[23:16] word(2/2) 10 16-bit ll x x r[15:8] r[7:0] triple byte(1/2) 00 16-bit ll x x r[31:24] r[23:16] triple byte(2/2) 10 16-bit lh x x r[15:8] x triple byte(1/2) 01 16-bit hl x x x r[23:16] triple byte(2/2) 10 16-bit ll x x r[15:8] r[7:0] half-word 00 16-bit ll x x r[15:8] r[7:0] half-word 10 16-bit ll x x r[15:8] r[7:0] byte 00 16-bit lh x x r[7:0] x byte 01 16-bit hl x x x r[7:0] byte 10 16-bit lh x x r[7:0] x byte 11 16-bit hl x x x r[7:0] word(1/4) 00 8-bit hl x x x r[31:24] word(2/4) 01 8-bit hl x x x r[23:16] word(3/4) 10 8-bit hl x x x r[15:8] word(4/4) 11 8-bit hl x x x r[7:0] triple byte(1/3) 00 8-bit hl x x x r[31:24] triple byte(2/3) 01 8-bit hl x x x r[23:16] triple byte(3/3) 10 8-bit hl x x x r[15:7] triple byte(1/3) 01 8-bit hl x x x r[23:16] triple byte(2/3) 10 8-bit hl x x x r[15:8] triple byte(3/3) 11 8-bit hl x x x r[7:0] half-word(1/2) 00 8-bit hl x x x r[15:8] half-word(2/2) 01 8-bit hl x x x r[7:0] half-word(1/2) 10 8-bit hl x x x r[15:8] half-word(2/2) 11 8-bit hl x x x r[7:0] byte 00 8-bit hl x x x r[7:0] byte 01 8-bit hl x x x r[7:0] byte 10 8-bit hl x x x r[7:0] byte 11 8-bit hl x x x r[7:0] * 1) selected by memory configuration 0 register bankxconf[1:0]. www.datasheet.in chapter 4 biu module 4-14 table 4.3.7 access mapping (dram/hdram in big-endian mode) access ha[1:0] data bus width ( * 1) casb[3:0] * ( * 2) db[31:24] db[23:16] db[15:8] db[7:0] word 00 32-bit llll r[31:24] r[23:16] r[15:8] r[7:0] triple byte 00 32-bit lllh r[31:24] r[23:16] r[15:8] x triple byte 01 32-bit hlll x r[23:16] r[15:8] r[7:0] half-word 00 32-bit llhh r[15:8] r[7:0] x x half-word 10 32-bit hhll x x r[15:8] r[7:0] byte 00 32-bit lhhh r[7:0] x x x byte 01 32-bit hlhh x r[7:0] x x byte 10 32-bit hhlh x x r[7:0] x byte 11 32-bit hhhl x x x r[7:0] word(1/2) 00 16-bit hhll x x r[31:24] r[23:16] word(2/2) 10 16-bit hhll x x r[15:8] r[7:0] triple byte(1/2) 00 16-bit hhll x x r[31:24] r[23:16] triple byte(2/2) 10 16-bit hhlh x x r[15:8] x triple byte(1/2) 01 16-bit hhhl x x x r[23:16] triple byte(2/2) 10 16-bit hhll x x r[15:8] r[7:0] half-word 00 16-bit hhll x x r[15:8] r[7:0] half-word 10 16-bit hhll x x r[15:8] r[7:0] byte 00 16-bit hhlh x x r[7:0] x byte 01 16-bit hhhl x x x r[7:0] byte 10 16-bit hhlh x x r[7:0] x byte 11 16-bit hhhl x x x r[7:0] * 1) selected by memory configuration 0 register bankxconf[1:0]. * 2) asserted for both read access and write access. www.datasheet.in chapter 4 biu module 4-15 table 4.3.8 access mapping (csn and mcsn in big-endian mode) access ha[1:0] port size ( * 1) casb[3:0] * ( * 2) db[31:24] db[23:16] db[15:8] db[7:0] word 00 32-bit llll r[31:24] r[23:16] r[15:8] r[7:0] triple byte 00 32-bit lllh r[31:24] r[23:16] r[15:8] x triple byte 01 32-bit hlll x r[23:16] r[15:8] r[7:0] half-word 00 32-bit llhh r[15:8] r[7:0] x x half-word 10 32-bit hhll x x r[15:8] r[7:0] byte 00 32-bit lhhh r[7:0] x x x byte 01 32-bit hlhh x r[7:0] x x byte 10 32-bit hhlh x x r[7:0] x byte 11 32-bit hhhl x x x r[7:0] word(1/2) 00 16-bit llhh r[31:24] r[23:16] x x word(2/2) 10 16-bit llhh r[15:8] r[7:0] x x triple byte(1/2) 00 16-bit llhh r[31:24] r[23:16] x x triple byte(2/2) 10 16-bit lhhh r[15:8] x x x triple byte(1/2) 01 16-bit hlhh x r[23:16] x x triple byte(2/2) 10 16-bit llhh r[15:8] r[7:0] x x half-word 00 16-bit llhh r[15:8] r[7:0] x x half-word 10 16-bit llhh r[15:8] r[7:0] x x byte 00 16-bit lhhh r[7:0] x x x byte 01 16-bit hlhh x r[7:0] x x byte 10 16-bit lhhh r[7:0] x x x byte 11 16-bit hlhh x r[7:0] x x * 1) selected by memory configuration 0 register cs size (csn * ). port size for mcs * are fixed to 16 bit width. * 2) asserted for write access only. www.datasheet.in chapter 4 biu module 4-16 table 4.3.9 access mapping (pcmcia in big-endian mode) access ha[1:0] port size ( * 1) cardcsnl * , cardcsnh * db[31:24] db[23:16] db[15:8] db[7:0] word(1/2) 00 16-bit ll r[31:24] r[23:16] x x word(2/2) 10 16-bit ll r[15:8] r[7:0] x x triple byte(1/2) 00 16-bit ll r[31:24] r[23:16] x x triple byte(2/2) 10 16-bit lh r[15:8] x x x triple byte(1/2) 01 16-bit hl x r[23:16] x x triple byte(2/2) 10 16-bit ll r[15:8] r[7:0] x x half-word 00 16-bit ll r[15:8] r[7:0] x x half-word 10 16-bit ll r[15:8] r[7:0] x x byte 00 16-bit lh r[7:0] x x x byte 01 16-bit hl x r[7:0] x x byte 10 16-bit lh r[7:0] x x x byte 11 16-bit hl x r[7:0] x x word(1/2) 00 8-bit ll r[31:24] r[23:16] x x word(2/2) 10 8-bit ll r[15:8] r[7:0] x x triple byte(1/2) 00 8-bit ll r[31:24] r[23:16] x x triple byte(2/2) 10 8-bit lh r[15:8] x x x triple byte(1/2) 01 8-bit lh r[23:16] x x x triple byte(2/2) 10 8-bit ll r[15:8] r[7:0] x x half-word 00 8-bit ll r[15:8] r[7:0] x x half-word 10 8-bit ll r[15:8] r[7:0] x x byte 00 8-bit lh r[7:0] x x x byte 01 8-bit lh r[7:0] x x x byte 10 8-bit lh r[7:0] x x x byte 11 8-bit lh r[7:0] x x x * 1) selected by memory configuration 3 register port8sel www.datasheet.in chapter 4 biu module 4-17 4.3.3 cs3-cs0 and mcs3-mcs0 timing figure 4.3.1 through figure 4.3.4 show the timing for cs3-cs0 and mcs3-mcs0. the timing is the same for all these signals, with the only exception being that 32-bit port timing only applies to cs3-cs0 while 16-bit port timing applies to cs3-cs0 and mcs3-mcs0. timing is also shown for read page mode accesses. if read page mode is enabled, the chip select will be asserted for the entire read cycle. if the processor is performing a burst read to re-fill either a data or instruction cache line, the chip select will remain asserted for the entire burst read. the first access of a read page mode access uses the accval1 control bits to define the access time, while the next three accesses will use the accval2 control bits to define the access time. the pattern will repeat until the read is complete. figure 4.3.1 shows the timing for a single word read and write for a 32-bit memory device. the access time is defined using the accval1 control bits. there are separate accval1 control bits for each of the chip selects, such that each chip select has an independently configurable access time. the accval1 bits should be set to the desired number of clk times for the chip select. the accval1 bits must not be set to $0. figure 4.3.2 shows the timing for a word read from a 16-bit port. the access is split into two parts to read the full 32 bits. during the first read ha (1) will be low and during the second read ha (1) will be high. the input data path will latch both accesses and concatenate them together as 32 bits for the processor before asserting the ack signal to the cpu interface logic. figure 4.3.3 shows a 4-word burst read from a 32-bit port. the ale signal is only asserted at the beginning of the cycle since the upper address bits will not be changed during the burst. the burst will always start on a 16-byte boundary. the address bits will increment as follows: ha[3:2] = 00, ha[3:2] = 01, ha[3:2] = 10, then ha[3:2] = 11. figure 4.3.4 shows the same 4-word burst read from a 32-bit port, except this time read page mode is enabled. in this case the chip select will remain asserted for the entire access and the addresses will change to access the new address location. the first access uses the accval1 control bits, while the next three accesses use the accval2 control bits. if the burst had been longer then 4 words, the accval1 control bits would have been used for every fourth access. this type of bursting is compatible with rom devices that support page mode access. if the 4-word burst would have been from a 16-bit port, eight accesses would have been required, but the accval1 bits would still be used for the first and fifth access, while the accval2 bits would have been used for the rest. if read page mode is enabled for a particular chip select, then the accval1 and accval2 control bits must not be set to $0. the ?up arrow? markings on dclkout in figure 4.3.1 through figure 4.3.4 show the points where input data is sampled. www.datasheet.in chapter 4 biu module 4-18 figure 4.3.1 word read/write 32-bit port figure 4.3.2 word read 16-bit port rd * csx/mcsx * d[31:16] a[12:0] ale dclkout 2 accval1 2 accval1 we3-0 * rd * csx/mcsx * d[31:0] a[12:0] ale dclkout we * 2 accval1 2 accval1 www.datasheet.in chapter 4 biu module 4-19 figure 4.3.3 4-word burst read 32-bit port figure 4.3.4 4-word burst read 32-bit port read with page mode enabled 2 accval2+1 2 accval2+1 2 accval2+1 dclkout ale a[12:0] d[31:0] csx/mcsx * rd * 2 accval1 2 accval1 2 accval1 2 accval1 dclkout ale a[12:0] d[31:0] csx/mcsx * rd * 2 accval1 www.datasheet.in chapter 4 biu module 4-20 4.3.4 card 2 and card 1 there are three different types of accesses to the card: memory, attribute and i/o. memory space is accessed by reading or writing from or to the card memory locations. attribute or io space is accessed by reading or writing from or to the card io attribute* locations. if an attribute access is desired, the cardxioen ( = 1, 2) bit should be cleared. if an io access is desired, the cardxioen bit should be set. to support bi-directional buffering of the data bus to the cards, the carddir* signal provides direction control for the bi-directional buffer. the carddir* signal will be asserted during a read to either card 2 or card 1. there is separate access time control provided for memory access versus io attribute* access. cardxaccval is used to control the access time for memory accesses and cardxioaccval is used to control the access time for io or attribute access. adding one to either access value control setting will increase the access time by two clk periods. a value of $1 will result in an access time of 1 clk period. figure 4.3.5 through figure 4.3.7 show the different timing for memory, attribute and io accesses. if a word access is made to the card, the access will be split into two accesses in the same manner as is done for cs3-cs0 and mcs3-mcs0. read page mode is not supported for the cards since it is not supported by the pcmcia specification. www.datasheet.in chapter 4 biu module 4-21 figure 4.3.5 memory access to card figure 4.3.6 attribute access to card 4 cardxaccval?2 4 cardxaccval?2 dclkout ale a[12:0] d[31:16] cardxcsh * /l * rd * we * carddir * carddreg iord * iowr * dclkout ale a[12:0] d[31:16] cardxcsh * /l * rd * 4 cardxioaccval?2 4 cardxioaccval?2 we * carddir * carddreg iord * iowr * www.datasheet.in chapter 4 biu module 4-22 figure 4.3.7 i/o access to card the pcmcia specification provides for a wait* signal that allows the card to halt the bus cycle until the wait* signal is de-asserted. this allows the card to control the access time. the wait* signal will assert at the beginning of the cycle and the cycle should not terminate until the wait* signal becomes de-asserted. there are separate wait* signals provided for each card: wait2* and wait1*. the wait* signals are sampled on two consecutive rising edges of clk. if the wait* signal is low, the access time counter will freeze until the wait* signal goes high. this function will only occur if the wait function is enabled using the cardxwaiten control bit. if the wait function is not enabled, the wait* signal is ignored. figure 4.3.6 shows the timing for card wait accesses. figure 4.3.8 card wait timing dclkout ale a[12:0] d[31:16] cardxcsh * /l * rd * 4 cardxioaccval?4 4 cardxioaccval?4 we * carddir * carddreg iord * iowr * dclkout ale a[12:0] d[31:16] cardxcs * rd * waitx * www.datasheet.in chapter 4 biu module 4-23 4.3.5 cs0 size configuration in order for the system to boot properly when powered up for the first time, it is necessary that cs0 and it's associated control be initialized properly since this chip select is used for the boot rom. when reset is asserted, the accval1 and accval2 control bits for cs0 will be set to their maximum value and read page mode will be disabled. the port size, 16-bit or 32-bit, is configured using the testaiu input pin. if the testaiu pin is high during reset, cs0 is configured as a 32-bit port, and if testaiu is low during reset, cs0 is configured as a 16-bit port. the cpu module section discusses the testaiu pin in more detail. www.datasheet.in chapter 4 biu module 4-24 4.4 dram and sdram controller the dram and sdram controller generates the required control signals to interface to dram and sdram devices. two separate banks are supported and each bank can contain either dram or sdram, with the only restriction being that bank 1 cannot contain sdram if bank 0 contains dram. the dram and sdram controller supports 4-mbit, 16-mbit and 64-mbit devices in various bus configurations. in order to maximize the memory bandwidth, both the dram and sdram devices can be kept in page mode to complete burst read cycles and in-page write cycles. 4.4.1 memory chips supported table 4.4.1 shows the different dram and sdram chips that are supported by the dram and sdram controller. also shown is the row and column configuration for the supported chips. sdram chips also contain two banks that are selectable through the address space. table 4.4.1 supported dram and sdram chips number of bank row address column address memory size memory type ? 9 9 256 k 16 4-mbit dram ? 10 8 256 k 16 4-mbit dram ? 10 9 512 k 84-mbit dram ?10101 m 16 16-mbit dram ?119 1 m 16 16-mbit dram ?128 1 m 16 16-mbit dram ?1110 2 m 8 16-mbit dram ?129 2 m 8 16-mbit dram 2119 2 m 8 16-mbit sdram 2118 1 m 16 16-mbit sdram ?11114 m 16 64-mbit dram ?12104 m 16 64-mbit dram ?1211 8 m 8 64-mbit dram 21210 8 m 8 64-mbit sdram 2129 4 m 16 64-mbit sdram 2139 8 m 8 64-mbit sdram 4128 4 m 16 64-mbit sdram * 1 4129 8 m 16 128-mbit sdram * 1 * 1 four-bank sdram www.datasheet.in chapter 4 biu module 4-25 4.4.2 dram and sdram configurations table 4.4.2 shows the various combinations of dram and sdram chips that are supported. bank 1 and bank 0 are independently programmable so each can contain any of the combinations. the only restriction is that bank 1 cannot contain sdram if bank 0 contains dram. table 4.4.2 supported dram and sdram configurations row col memory size memory type # of chips 18, 17:9 18, 8:1 256 k 16 4-mbit dram 1 256 k 16 20, 19, 17:9 20, 18, 8:1 1 m 16 16-mbit dram 1 1 m 16 18, 20, 19, 17:9 8:1 1 m 16 16-mbit dram 1 1 m 16 22, 21, 19, 17:9 22, 20, 18, 8:1 4 m 16 64-mbit dram 1 4 m 16 19, 17:9 19, 18, 8:2 256 k 32 4-mbit dram 2 256 k 16 19, 17:9 20, 18, 8:2 512 k 32 4-mbit dram 4 512 k 8 21, 19, 17:9 21, 20, 18, 8:2 1 m 32 16-mbit dram 2 1 m 16 18, 20, 19, 17:9 21, 8:2 1 m 32 16-mbit dram 2 1 m 16 22, 21, 19, 17:9 22, 20, 18, 8:2 2 m 32 16-mbit dram 4 2 m 8 23, 21, 19, 17:9 23, 22, 20, 18, 8:2 4 m 32 64-mbit dram 2 4 m 16 23, 21, 19, 17:9 24, 22, 20, 18, 8:2 8 m 32 64-mbit dram 4 8 m 8 18, 20, 19, 17:9 18, , x, 8:0 2 m 8 16-mbit sdram 1 2 m 8 22, 18, 20, 19, 17:9 22, x, , 21, 8:0 8 m 8 64-mbit sdram 1 8 m 8 18, 20, 19, 17:9 18, , x, x, 8:1 1 m 16 16-mbit sdram 1 1 m 16 18, 20, 19, 17:9 18, , x, 21, 8:1 2 m 16 16-mbit sdram 2 2 m 8 22, 18, 20, 19, 17:9 22, x, , x, 21, 8:1 4 m 16 64-mbit sdram 1 4 m 16 22, 18, 20, 19, 17:9 22, x, , 23, 21, 8:1 8 m 16 64-mbit sdram 2 8 m 8 22, 18, 20, 19, 17:9 x, , x, 8:0 8 m 8 64-mbit sdram 1 8 m 8 22, 18, 20, 19, 17:9 22, x, , x, x, 8:1 4 m 16 64-mbit sdram 1 4 m 16 * 1 22, 18, 20, 19, 17:9 22, x, , 23, x, 8:1 8 m 16 64-mbit sdram 2 8 m 8 * 1, * 2 * 1 four-bank sdram * 2 when TMPR3911/12 and sdram are connected, a[8] and a[9] must be swapped. www.datasheet.in chapter 4 biu module 4-26 4.4.3 dram (1) dram dram in bank 1 is controlled using ras1* and cas3*-cas0*, while dram in bank 0 is controlled using ras0* and cas3*-cas0*. the memory configuration 0 register provides control bits that allow bank 1 or bank 0 to be independently set as either 32-bit or 16-bit dram configurations. the 32-bit dram configurations are connected to all 32 data bus bits d[31:0], while 16-bit dram configurations are connected to d[15:0] when the tmpr3912 is mapped as big endian. the 16-bit dram configurations will only use cas1* and cas0* for control, while 32-bit configurations will use all four cas* lines. word and tri accesses to 16-bit configured drams will be split into two accesses in the same manner as was done for the chip selects, except that the data is connected to d[15:0] instead of d[31:16]. connecting dram devices to the lower data bus and chip select memory devices to the upper data bus helps to balance the capacitive loading on the data bus. the dram timing is fixed to support 80 ns devices or faster. the only programmability is the enbank1opt and enbank0opt control bits in the memory configuration 4 register that allow an extra clock of time for the first access to the dram. this option is implemented to support 80 ns dram devices with a clock greater than 70 mhz for the cpu and biu. drams faster than 80 ns will not need the enbankxopt bit to be set. (drams faster than 160 ns will not need the enbankxopt bit to be set in case of TMPR3911.) during a burst read cycle the rasx* line will be asserted to latch the row address into the dram, and the cas* signals are then asserted for the required number of accesses. page mode writes are supported when the enwrinpage control bit is set in the memory configuration 0 register. an in- page write will occur when the cpu interface asserts the wrinpage signal during a write. if this signal is asserted, the dram will be kept in page mode until the wrinpage signal is no longer asserted. refresh is inserted using cas* before ras* refresh. the refresh control is generated by the arbitration logic. figure 4.4.1 through figure 4.4.4 show various timing examples, with refresh timing shown in figure 4.4.1. the timing is the same for 32-bit and 16-bit ports, except there are twice as many accesses to the 16-bit port. for example, a word read from a 16-bit port will result in a burst of two 16-bit reads to fetch the 32-bits of data. www.datasheet.in chapter 4 biu module 4-27 enbankxopt = 0 enbankxhdram = 0 figure 4.4.1 burst read followed by word write (dram) enbankxopt = 0 enbankxhdram = 1 figure 4.4.2 burst read followed by word write (hdram) enbankxopt = 0 enbankxhdram = 0 figure 4.4.3 in-page write (dram) dclkout a[12:0] d[31:0] ras * cas * we * dclkout a[12:0] d[31:0] ras * cas * we * row col col col col row col row col col col col col dclkout a[12:0] d[31:0] ras * cas * we * row col col col col row col col www.datasheet.in chapter 4 biu module 4-28 enbankxopt = 1 enbankxhdram = 0 figure 4.4.4 write with enbankopt set followed by refresh cycle (dram) (2) dram initialization when the dram is first powered up there are several things that must be done before accessing the dram. first the memory configuration registers must be properly configured for the chosen dram and bus configuration. next, after a delay of at least 100 s after the power is asserted to the dram, the refresh should be enabled. the dram should not be accessed until at least eight cas* before ras* refresh cycles occur. after this procedure is completed the dram can be accessed. dclkout a[12:0] d[31:0] ras * cas * we * row col www.datasheet.in chapter 4 biu module 4-29 4.4.4 sdram (1) sdram sdram devices are supported in bank 1 and bank 0. each bank can independently be configured to support either 16-bit or 8-bit sdrams. bank 1 uses ras1* as the chip select for the sdram and bank 0 uses dcs0*. all other control signals are shared between the two banks. the clock for the sdram devices is the dclkout signal which nominally runs at the clock twice the rate of the clk signal. reads from the sdrams occur on every dclkout cycle, such that the reading of all 32 bits for 16-bit sdrams can happen within a single clk cycle. a 16-bit sdram configuration provides the maximum memory bandwidth and once a read cycle begins, the cpu will not stall since 32 bits are read on each cycle. all 8-bit sdrams require 2 clk cycles to read 32 bits of data. during a burst read the sdram devices are kept in page mode for the entire read cycle. the sdram devices are also kept in page mode during in-page write cycles. all 16-bit sdrams can keep up at 32 bits per clk cycle, which can provide a long write block without stalling the cpu. all 8-bit sdrams require twice the number of cycles. tri, half-word and byte writes are supported to the sdram devices using the dqmh and dqml signals. these signals provide a data mask so that only the desired bytes will be written. dqmh is used for the upper 8 bits in a 16-bit sdram configuration and dqml is used for the lower 8 bits. for 8-bit sdrams only dqml is used. the data mask signals dqmh and dqml are required because the sdram is setup to always read or write 32 bits of data at a time. the data mask signals will ?mask out? the bytes that should not be written during partial word stores. (2) sdram initialization prior to accessing an sdram device, an initialization procedure must be followed. first, all memory configuration registers must be properly initialized for the chosen sdram and bus configuration. next, after a pause of at least 200 s after power is applied to the sdram, a command must be sent to precharge the sdram banks. the command is sent by writing to the sdram bank 1 and/or bank 0 mode register address with data[31] set high when the TMPR3911/12 is mapped as big endian, or with data[7] set high when the TMPR3911/12 is mapped as little endian. setting this bit will cause a precharge all command to be sent to the sdram instead of writing to the mode register. next, the mode register must be properly initialized. finally, refresh should be enabled and at least 8 refresh cycles must occur prior to reading or writing from or to the sdram. (3) sdram mode register an sdram contains a write-only mode register that defines the parameters for accessing the device. the mode register must be initialized prior to reading or writing from the sdram. they can be written via the sdram bank 1 and sdram bank 0 addresses as shown in the system address map. when writing to the mode register, the data from the cpu interface on data[12:0] (data[20:16, 31:24]) is placed on a[12:0], and data[31] (data[7]) must be a zero when the TMPR3911/12 is mapped as big endian (little endian). this is done because the mode register receives its data on the address bus instead of the data bus. the sdram should be configured for the following settings: burst length = 4 (for 8-bit sdram) or burst length = 2 (for 16-bit sdram), cas latency = 3, burst type = sequential, write mode = burst write. www.datasheet.in chapter 4 biu module 4-30 (4) sdram power down mode the dcke signal is provided for putting the sdram into power down mode. the power down mode feature can be enabled or disabled using the ensdrampd control bit in the memory configuration 0 register. when this bit is set, the dcke signal will be held low whenever there are no accesses to the sdram device for 7 clk periods. once a read, write or refresh is initiated to the sdram, the dcke signal is asserted to bring the device out of power down mode. power down mode helps to reduce power dissipation in the sdram device when there are no accesses. during memory power down the sdram device is placed into self refresh mode for maximum power savings and the dclkout signal. (5) sdram timing figure 4.4.5 through figure 4.4.7 show a few examples of the sdram timing. the first chip select (assertion of cs*) is used to latch the row address. subsequent chip selects will either read or write data, and the final chip select is used to precharge the bank. note from table 4.4.2 that address bit 10 for 16-mbit parts and address bit 11 for 64-mbit parts is always a zero during the column address. this is done to ensure that auto precharge is never latched during a read or write command and also will cause only the bank that is being accessed to be precharged during the precharge command. since the burst size of the sdrams is always setup to 32 bits, reads will always be 32 bits without regard to the actual number of bytes requested by the cpu. writes are also 32 bits, but the data mask signals dqmh and dqml will mask out the bytes that should not be written, thus allowing for triple byte, half-word and byte writes. figure 4.4.5 word read and write to 8-bit sdram dclkout a[12:0] d[7:0] dcs0/1 * ras * cas * we * row row column column 32-bit read 32-bit write dqmh dqml dcke www.datasheet.in chapter 4 biu module 4-31 figure 4.4.6 word read and write to 16-bit sdram figure 4.4.7 4-word burst read and byte write to 16-bit sdram (6) support of four-bank sdram (only by TMPR3911bu/bxb and tmpr3912xb-92/au-92) the tmpr3912xb-92/au-92 supports four-bank sdram. when dram banks 0 and 1 are 16-bit sdram, addr[21] is output from the cas2* pin. also, by setting row and col as follows, addr[22] can be output from the a[12] pin. row: 22, 18, 20, 19, 17:9 (rowsel = 01) col: 22, x, , x, x, 8:1 (colsel = 1000) the cas2* pin (addr[21]) and a[12] pin (addr[22]) can be connected to the four-bank sdram bank select pin so that the cas2* and a[12] pins are used for the bank select signal. dclkout a[12:0] d[7:0] dcs0/1 * ras * cas * we * row row column column 32-bit 32-bit write dqmh dqml dcke dclkout a[12:0] d[7:0] dcs0/1 * ras * cas * we * row col column 4 word burst read byte write dqmh dqml dcke col col row column www.datasheet.in chapter 4 biu module 4-32 4.5 arbitration the arbitration logic contains the refresh controller for bank 1 and bank 0, support for external bus master, the watch dog timer for terminating hung memory accesses, and memory power down logic for placing the sdram and/or dram into self refresh mode. 4.5.1 refresh controller the refresh controller logic contains separate refresh counters for bank 1 and bank 0. each counter is a 6-bit counter that uses the 32 khz clock for the counter. the refresh rate is set using the rfshval1[5:0] and rfshval0[5:0] control bits in the memory configuration 4 register. these values are loaded into the respective refresh counter. the refresh counter will down count and when it reaches a count of zero, refresh will be inserted. if the rfshvalx control bits are set to $00, the counter is not used and instead refresh is generated based on both the rising and falling edge of the 32 khz clock. this is required to generate a 15.26 s refresh rate required by some drams or sdrams. rfshvalx control bits set to $01 will cause a refresh rate of 61.04 s and additional values will increase the refresh rate by increments of 30.52 s. when it is time for the refresh controller to insert refresh, the halt signal will be asserted to the cpu interface. once the cpu interface asserts the halted signal, the refresh controller will generate the appropriate control signals that will cause the dram & sdram control logic to provide refresh for the memory devices. once the refresh controller has completed inserting refresh, the halt signal will be de-asserted so that the cpu interface can continue running. 4.5.2 external bus master the external bus master logic allows an external device to take control of the memory signals so that memory can be shared with an external device. the external device will request the bus by asserting the dreq* signal. once the dreq* signal is asserted, the halt signal will be asserted to the cpu interface logic. once the cpu interface logic asserts the halted signal, the external bus master logic will then assert the dgrnt* signal to inform the external device that it now controls the memory bus. at the same time that dgrnt* is asserted, the following signals are tri-stated: d[31:0], a[12:0], ale, rd*, we*, cas3*-cas0*, ras1*, ras0*, dcs0*, dcke, dqmh, dqml and cs0*. dclkout will be tri-stated if the endclkouttri control bit is set in the memory configuration 0 register. otherwise, dclkout will continue to run. once the external device de-asserts dreq*, dgrnt* will be de- asserted, the memory signals will be driven by the TMPR3911/12, and the halt signal will be de- asserted so the cpu interface can begin launching memory transactions. the external device should not attempt to take over the memory signals for a long period of time, otherwise TMPR3911/12 dma events and refresh will be interrupted. the external bus master logic will not respond with a dgrnt* if the memory interface is powered down. www.datasheet.in chapter 4 biu module 4-33 4.5.3 watch dog timer the watch dog timer prevents accesses to reserved memory locations from hanging the biu. the watch dog timer consists of a 10-bit down-counter whose initial value is determined by the watchtimeval[3:0] control bits in the memory configuration 4 register. the watchtimeval[3:0] control bits are loaded into the upper 4 bits of the 10-bit counter and the lower 6 bits are loaded with $3f. the counter uses the clk signal to count. the watch dog timer rate is determined by the following equation: watch dog timer rate = 1) ( clk f 64 1) 0] : val[3 (watchtime * * + * 1f clk is the frequency of the clk signal and is 4 the frequency of sysclk (that is, when sysclk is 9.216 mhz, f clk is 36.864 mhz ( * 2); when sysclk is 11.520 mhz, f clk is 46.08 mhz. * 2 note that these valve is the case that the rf function is not used. therefore, in case of TMPR3911, f clk is a half of this valve, which means 18.432 mhz the watch dog timer is enabled using the enwatch control bit in the memory configuration 4 register. when enabled, the counter will load whenever the cpu interface asserts the start signal to begin a memory transaction. if the watch dog timer reaches a count of zero before the memory state machine asserts the ack signal, the buserror signal is asserted to end the memory transaction. there are two possible ways that this can occur. first, if the address provided by the cpu interface to the address decoder is pointing to any of the reserved locations or to any of the chip selects that are not enabled, then the memory state machine will not respond with an ack. secondly, if the wait function is enabled to card 2 or card 1, then the wait2* or wait1* signals must de-assert before the watch dog timer reaches a count of zero, otherwise the buserror signal will be asserted and the card access will be aborted. 4.5.4 memory power down the memory interface is powered down whenever the mempowerdown control bit is set in the memory configuration 4 register. when this bit is set, the halt signal will be asserted to the cpu interface, the dram and/or sdram will be placed into self refresh mode, and all memory interface signals will be driven low. the memory interface will wake up whenever the cpu interface asserts the haltcycle signal and the address defined by the addr[31:2] bits correspond to an address other than internal function registers. when the memory interface wakes up, the dram and/or sdram are taken out of self refresh mode and the halt signal is de-asserted to allow the cpu interface to launch memory transactions. figure 4.5.1 and figure 4.5.2 show timing for the wake-up and power-down of the memory interface. www.datasheet.in chapter 4 biu module 4-34 figure 4.5.1 memory interface wake-up figure 4.5.2 memory interface power down when the memory interface is powered down all memory signals are driven low. the order in which they are driven low is important because dram devices enter self refresh mode by asserting cas* before ras*, and sdram devices enter self refresh mode by de-asserting dcke while dcs0* and/or ras1*, ras0* and cas0* are asserted with we* not asserted. once the sdram enters self refresh mode, dclkout can be turned off. the ordering makes it possible to put both dram and sdram devices into self refresh mode with only one time setting required. when the memory interface comes out of self refresh mode, all signals are de-asserted. dcke must de-assert one clock later in order to properly bring the sdram out of self refresh mode. after exiting self refresh mode, the halt signal will not be released for several clocks to allow the dram and sdram to finish exiting self refresh mode. dclkout a[12:0] d[31:0] dcs0 * ras1 * ras0 * cas3-0 * we * dqmh/l dcke dclkout a[12:0] d[31:0] dcs0 * ras1 * ras0 * cas3-0 * we * dqmh/l dcke www.datasheet.in chapter 4 biu module 4-35 4.6 memory connections data bus pins (d[31:0]), cas signal pins, and data mask pins (dqmh, dqml) change their functions in big endian and little endian. the following table shows the change of the name of each pin in big endian and little endian. (the endian can be selected using the endian pin, ?1? level to the big endian, ?0? level to the little endian.) pin no. TMPR3911bu TMPR3911bxb tmpr3912au tmpr3912xb big endian little endian 114 p7 133 h12 d[31] d[7] 115 n7 134 g10 d[30] d[6] 116 m6 136 g14 d[29] d[5] 117 r7 138 g12 d[28] d[4] 118 n6 139 g11 d[27] d[3] 120 m5 141 f14 d[26] d[2] 121 r6 143 f12 d[25] d[1] 123 p5 145 e14 d[24] d[0] 124 n4 146 e13 d[23] d[15] 125 r5 148 d15 d[22] d[14] 127 n3 150 d13 d[21] d[13] 128 p3 152 c15 d[20] d[12] 129 r4 153 c14 d[19] d[11] 131 r3 155 b14 d[18] d[10] 133 p1 157 a15 d[17] d[9] 136 n2 159 e11 d[16] d[8] 20 c7 27 h1 d[15] d[23] 19 d7 26 h3 d[14] d[22] 18 c8 24 g6 d[13] d[21] 17 a7 23 g1 d[12] d[20] 16 b6 21 g3 d[11] d[19] 14 d6 19 f1 d[10] d[18] 13 a6 18 g5 d[9] d[17] 12 b5 16 f3 d[8] d[16] 11 c5 14 f4 d[7] d[31] 10 b4 12 e3 d[6] d[30] 9 a5 11 d1 d[5] d[29] 7 c49d2d[4]d[28] 5 a4 7 c1 d[3] d[27] 4 b3 5 c2 d[2] d[26] 3 a1 4 b1 d[1] d[25] 2 a3 2 c3 d[0] d[24] 166 e3 195 d6 cas3 * cas0 * 167 e2 197 b5 cas2 * cas1 * 168 d3 198 c5 cas1 * cas2 * 169 e1 199 e6 cas0 * cas3 * 175 c1 207 b2 dqmh dqml 176 b1 208 a2 dqml dqmh www.datasheet.in chapter 4 biu module 4-36 figure 4.6.1 through figure 4.6.8 illustrate the various signal connections between the TMPR3911/12 and external sdram, dram, and static memory devices. these figures show the connections for various bus width configurations (e.g., 8-bit, 16-bit, 32-bit). figure 4.6.1 sdram memory connection (big endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 dclkin dclkout a[12:0] dqml dqmh dcke dcs0 * ras0 * ras1 * cas0 * d[15:8] we * d[7:0] pin no. 171,...189 199 clk a12-0 dqml dqmh cke ras * cs * cas * d15-8 we * d7-0 194 192 bank1: 16-bit sdram 193 169 202 207 208 205 204 27,...16 14,...2 dclkout a[12:0] dqml dqmh dcke dcs0 * ras0 * dcs1 * cas0 * d[15:8] we * d[7:0] clk a12-0 dqm cke ras * cs * cas * we * d7-0 bank0: 8-bit sdram a[12:0] dcs0 * ras0 * cas0 * dclkout dqml dcke d[7:0] we * * 1 www.datasheet.in chapter 4 biu module 4-37 figure 4.6.2 sdram memory connection (little endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 dclkin dclkout a[12:0] dqmh dqml dcke dcs0 * ras0 * ras1 * cas3 * d[23:16] we * d[31:24] pin no. 171,...189 199 clk a12-0 dqmh dqml cke ras * cs * cas * d7-0 we * d15-8 194 192 bank1: 16-bit sdram 193 169 202 207 208 205 204 27,...16 14,...2 dclkout a[12:0] dqmh dqml dcke dcs0 * ras0 * dcs1 * cas3 * d[23:16] we * d[31:24] clk a12-0 dqm cke ras * cs * cas * we * d7-0 bank0: 8-bit sdram a[12:0] dcs0 * ras0 * cas3 * dclkout dqmh dcke d[31:24] we * * 1 www.datasheet.in chapter 4 biu module 4-38 figure 4.6.3 4-bank sdram memory connection (big endian) * (supported only by tmpr3912xb-92/au-92) * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of tmpr3912xb-92 (fbga217), refer to the table in the section 2. * 2 a[8] and a[9] must be swapped when 128 mbit sdram is used. tmpr3912 dclkin dclkout a[11:0] dqml dqmh dcke dcs0 * ras0 * ras1 * cas0 * we * pin no. 172,...189 199 clk a11-0 dqml dqmh cke bs0 cs * bs1 d15-8 we * d7-0 194 192 bank1: 16-bit sdram 193 169 202 207 208 205 204 27,...16 14,...2 dclkout a[11:0] dqml dqmh dcke dcs0 * ras0 * dcs1 * cas0 * d[15:8] we * d[7:0] dqml a11-0 dqmh cke ras * cs * cas * we * bank0: 16 -bit sdram a[11:0] dcs0 * ras0 * cas0 * dclkout dqml dcke d[7:0] we * d7-0 d[15:8] d[7:0] a[12] cas2 * 197 171 bs0 (addr21) bs1 (addr22) ras * cas * clk d15-8 bs0 bs1 d[15:8] dqmh bs0 (addr21) bs1 (addr22) * 1 * 2 * 2 www.datasheet.in chapter 4 biu module 4-39 figure 4.6.4 4-bank sdram memory connection (little endian) * (supported only by tmpr3912xb-92/au-92) * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of tmpr3912xb-92 (fbga217), refer to the table in the section 2. * 2 a[8] and a[9] must be swapped when 128 mbit sdram is used. tmpr3912 dclkin dclkout a[11:0] dqmh dqml dcke dcs0 * ras0 * ras1 * cas3 * we * pin no. 172,...189 199 clk a11-0 dqmh dqml cke bs0 cs * bs1 d7-0 we * d15-8 194 192 bank1: 16-bit sdram 193 169 202 207 208 205 204 27,...16 14,...2 dclkout a[11:0] dqmh dqml dcke dcs0 * ras0 * dcs1 * cas3 * d[23:16] we * d[31:24] dqmh a11-0 dqml cke ras * cs * cas * we * bank0: 16-bit sdram a[11:0] dcs0 * ras0 * cas0 * dclkout dqmh dcke d[31:24] we * d15-8 d[23:16] d[31:24] a[12] cas1 * 197 171 bs0 (addr21) bs1 (addr22) ras * cas * clk d7-0 bs0 bs1 d[23:16] dqml bs0 (addr21) bs1 (addr22) * 1 * 2 * 2 www.datasheet.in chapter 4 biu module 4-40 figure 4.6.5 dram memory connection (big endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 a[12:0] cas1 * cas2 * cas0 * cas3 * d[15:8] we * d[7:0] pin no. 171,...189 195 a12-0 we ras * cas * mh cas * lo cas * hi d15-8 cas * ml d7-0 197 198 bank1: 32-bit dram 199 194 27,...16 14,...2 d[23:16] a[12:0] d[31:24] we * ras1 * cas1 * cas2 * cas0 * cas3 * d[15:8] ras0 * d[7:0] a12-0 d15-8 ras * lo ras * cas * hi we * d7-0 bank0: 16-bit dram a[12:0] ras0 * cas0 * cas1 * d[7:0] we * d[15:8] d[31:24] d[23:16] ras1 * ras0 * d31-24 d23-16 133,...145 146,...159 193 169 * 1 www.datasheet.in chapter 4 biu module 4-41 figure 4.6.6 dram memory connection (little endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 a[12:0] cas2 * cas1 * cas3 * cas0 * d[23:16] we * d[31:24] pin no. 171,...189 195 a12-0 we ras * cas * ml cas * hi cas * lo d23-16 cas * mh d31-24 197 198 bank1: 32-bit dram 199 194 27,...16 14,...2 d[15:8] a[12:0] d[7:0] we * ras1 * cas2 * cas1 * cas3 * cas0 * d[23:16] ras0 * d[31:24] a12-0 d7-0 ras * hi ras * cas * lo we * d15-8 bank0: 16-bit dram a[12:0] ras0 * cas3 * cas2 * d[31:24] we * d[23:16] d[7:0] d[15:8] ras1 * ras0 * d7-0 d15-8 133,...145 146,...159 193 169 * 1 www.datasheet.in chapter 4 biu module 4-42 figure 4.6.7 chip select memory connection (big endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 a[12:0] cas1 * cas2 * cas0 * cas3 * d[15:8] rd * d[7:0] pin no. 171,...189 126 addr oe * we * mh we * lo we * hi d15-8 we * ml d7-0 125 195 cs2: 32 bit 197 198 27,...16 14,...2 d[23:16] a[12:0] d[31:24] d[15:8] d[7:0] addr d15-8 we * hi we * lo cs * oe * d7-0 cs1: 16 bit ha[25:0] we2 * we3 * cs1 * d[23:16] rd * d[31:24] d[31:24] d[23:16] d31-24 d23-16 133,...145 146,...159 199 163 ale cs1 * cs2 * 168 we1 * we2 * we0 * we3 * rd * cs1 * cs2 * ale cs * latch le 13 13 * 1 www.datasheet.in chapter 4 biu module 4-43 figure 4.6.8 chip select memory connection (little endian) * * 1 note that pin no. in the figure above are those of tmpr3912au-92 (lqfp208). in case of TMPR3911bu (lqfp176), TMPR3911bxb (fbga177) and tmpr3912xb-92 (fbga217), refer to the table in the section 2. TMPR3911/12 a[12:0] cas2 * cas1 * cas3 * cas0 * d[23:16] rd * d[31:24] pin no. 171,...189 126 addr oe * we * ml we * hi we * lo d23-16 we * mh d31-24 125 195 cs2: 32 bit 197 198 27,...16 14,...2 d[15:8] a[12:0] d[7:0] d[23:16] d[31:24] addr d7-0 we * lo we * hi cs * oe * d15-8 cs1: 16 bit ha[25:0] we1 * we0 * cs1 * d[15:8] rd * d[7:0] d[7:0] d[15:8] d7-0 d15-8 133,...145 146,...159 199 163 ale cs1 * cs2 * 168 we2 * we1 * we3 * we0 * rd * cs1 * cs2 * ale cs * latch le 13 13 * 1 www.datasheet.in chapter 4 biu module 4-44 4.7 biu registers 4.7.1 memory configuration 0 register offset = $000: bit label reset read/write 31 reserved 30 endclkouttri 0 r/w 29 disdqminit 0 r/w 28 ensdrampd 0 r/w 27 showdino 0 r/w 26 enrmap2 0 r/w 25 enrmap1 0 r/w 24 enwrinpage 0 r/w 23 encs3user x r/w 22 encs2user x r/w 21 encs1user x r/w 20 encs1dram x r/w 19-18 bank1conf[1:0] x r/w 17-16 bank0conf[1:0] x r/w 15-14 rowsel1[1:0] x r/w 13-12 rowsel0[1:0] x r/w 11-8 colsel1[3:0] x r/w 7-4 colsel0[3:0] x r/w 3 cs3size x r/w 2 cs2size x r/w 1 cs1size x r/w 0 cs0size see description r/w endclkouttri: setting this bit will cause the dclkout pin to tri-state when dgrnt* is asserted during external bus arbitration. otherwise, dclkout will continue to operate. disdqminit: if this bit is a cleared, the dqmh and dqml signals will go high when coming out of power- down and remain high until the first access to sdram. if this bit is set, this function is disabled and the dqmh and dqml signals will remain low. ensdrampd: setting this bit will cause the biu to put the sdrams into power down mode by lowering dcke whenever there are no accesses to the sdrams for 7 clk periods. showdino: setting this bit will cause internal reads and writes by the processor to function registers to show externally for debug. the rd* signal provides the read or write status, d[31:0] provide the data, a[12:0] provide the address, and the cardreg* signal provides a chip select on the rising edge for sampling the signals. enrmap2: setting this bit will enable address re-mapper 2. www.datasheet.in chapter 4 biu module 4-45 enrmap1: setting this bit will enable address re-mapper 1. enwrinpage: setting this bit will cause the drams and/or sdrams to remain in page mode when the wrinpage signal is asserted by the cpu interface. if this bit is cleared, the wrinpage signal is ignored. encs3user: setting this bit will enable cs3 in the kuseg space. encs2user: setting this bit will enable cs2 in the kuseg space. encs1user: setting this bit will enable cs1 in the kuseg space. encs1dram: setting this bit will enable cs1 in bank 1 and bank 0 space. bank1conf[1:0]: these bits provide the configuration for bank 1 according to the following: 11 16-bit sdram 10 8-bit sdram 01 32-bit dram/hdram 00 16-bit dram/hdram bank0conf[1:0]: these bits provide the configuration for bank 0 according to the following: 11 16-bit sdram 10 8-bit sdram 01 32-bit dram/hdram 00 16-bit dram/hdram www.datasheet.in chapter 4 biu module 4-46 rowsel1[1:0]: rowsel0[1:0]: colsel1[3:0]: colsel0[3:0]: these bits determine the row and column configuration for addressing according to the following: row rowsel col colsel 18, 17:9 00 22, 20, 18, 8:1 0000 22, 18, 20, 19, 17:9 01 19, 18, 8:2 0001 20, 22, 21, 19, 17:9 10 21, 20, 18, 8:2 0010 22, 23, 21, 19, 17:9 11 23, 22, 20, 18, 8:2 0011 24, 22, 20, 18, 8:2 0100 18, , x, 8:0 0101 22, x, , 21, 8:0 0110 18, , x, 21, 8:1 0111 22, x, , 23, 21, 8:1 1000 24, 23, 21, 8:2 1001 reserved others cs3size: setting this bit defines cs3 to be a 32-bit port. otherwise, a 16-bit port is assumed. cs2size: setting this bit defines cs2 to be a 32-bit port. otherwise, a 16-bit port is assumed. cs1size: setting this bit defines cs1 to be a 32-bit port. otherwise, a 16-bit port is assumed. cs0size: setting this bit defines cs0 to be a 32-bit port. otherwise, a 16-bit port is assumed. on reset, this signal is set high if the testaiu pin is tied high and low if the testaiu pin is tied low. www.datasheet.in chapter 4 biu module 4-47 4.7.2 memory configuration 1 register offset = $004 bit label reset read/write 31-28 mcs3accval1[3:0] x r/w 27-24 mcs3accval2[3:0] x r/w 23-20 mcs2accval1[3:0] x r/w 19-16 mcs2accval2[3:0] x r/w 15-12 mcs1accval1[3:0] x r/w 11-8 mcs1accval2[3:0] x r/w 7-4 mcs0accval1[3:0] x r/w 3-0 mcs0accval2[3:0] x r/w mcs3accval1[3:0]: these bits define the access time for mcs3. if enmcs3page is set, these bits will be used for the first access and mcs3accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if enmcs3page is not set, these bits and mcs3accval2[3:0] should be set with the same value. if enmcs3page is set, these bits must be set to at least $1. mcs3accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if enmcs3page is set. if enmcs3page is not set, these bits and mcs3accval1[3:0] should be set with the same value. if enmcs3page is set, these bits must be set to at least $2. mcs2accval1[3:0]: these bits define the access time for mcs2. if enmcs2page is set, these bits will be used for the first access and mcs2accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if enmcs2page is not set, these bits and mcs2accval2[3:0] should be set with the same value. if enmcs2page is set, these bits must be set to at least $1. mcs2accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if enmcs2page is set. if enmcs2page is not set, these bits and mcs2accval1[3:0] should be set with the same value. if enmcs2page is set, these bits must be set to at least $2. mcs1accval1[3:0]: these bits define the access time for mcs1. if enmcs1page is set, these bits will be used for the first access and mcs1accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if enmcs1page is not set, these bits and mcs1accval2[3:0] should be set with the same value. if enmcs1page is set, these bits must be set to at least $1. mcs1accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if enmcs1page is set. if enmcs1page is not set, these bits and mcs1accval1[3:0] should be set with the same value. if enmcs1page is set, these bits must be set to at least $2. www.datasheet.in chapter 4 biu module 4-48 mcs0accval1[3:0]: these bits define the access time for mcs0. if enmcs0page is set, these bits will be used for the first access and mcs0accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if enmcs0page is not set, these bits and mcs0accval2[3:0] should be set with the same value. if enmcs0page is set, these bits must be set to at least $1. mcs0accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if enmcs0page is set. if enmcs0page is not set, these bits and mcs0accval1[3:0] should be set with the same value. if enmcs0page is set, these bits must be set to at least $2. 4.7.3 memory configuration 2 register offset = $008 bit label reset read/write 31-28 cs3accval1[3:0] x r/w 27-24 cs3accval2[3:0] x r/w 23-20 cs2accval1[3:0] x r/w 19-16 cs2accval2[3:0] x r/w 15-12 cs1accval1[3:0] x r/w 11-8 cs1accval2[3:0] x r/w 7-4 cs0accval1[3:0] $f r/w 3-0 cs0accval2[3:0] $f r/w cs3accval1[3:0]: these bits define the access time for cs3. if encs3page is set, these bits will be used for the first access and cs3accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if encs3page is not set, these bits and cs3accval2[3:0] should be set with the same value. if encs3page is set, these bits must be set to at least $1. cs3accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if encs3page is set. if encs3page is not set, these bits and cs3accval1[3:0] should be set with the same value. if encs3page is set, these bits must be set to at least $2. cs2accval1[3:0]: these bits define the access time for cs2. if encs2page is set, these bits will be used for the first access and cs2accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if encs2page is not set, these bits and cs2accval2[3:0] should be set with the same value. if encs2page is set, these bits must be set to at least $1. cs2accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if encs2page is set. if encs2page is not set, these bits and cs2accval1[3:0] should be set with the same value. if encs2page is set, these bits must be set to at least $2. www.datasheet.in chapter 4 biu module 4-49 cs1accval1[3:0]: these bits define the access time for cs1. if encs1page is set, these bits will be used for the first access and cs1accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if encs1page is not set, these bits and cs1accval2[3:0] should be set with the same value. if encs1page is set, these bits must be set to at least $1. cs1accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if encs1page is set. if encs1page is not set, these bits and cs1accval1[3:0] should be set with the same value. if encs1page is set, these bits must be set to at least $2. cs0accval1[3:0]: these bits define the access time for cs0. if encs0page is set, these bits will be used for the first access and cs0accval2[3:0] will be used for the next three accesses for reads only. for writes, only these bits are used. if encs0page is not set, these bits and cs0accval2[3:0] should be set with the same value. if encs0page is set, these bits must be set to at least $1. cs0accval2[3:0]: these bits define the access time for the next three reads in a burst sequence if encs0page is set. if encs0page is not set, these bits and cs0accval1[3:0] should be set with the same value. if encs0page is set, these bits must be set to at least $2. 4.7.4 memory configuration 3 register offset = $00c bit label reset read/write 31-28 card2accval[3:0] x r/w 27-24 card1accval[3:0] x r/w 23-20 card2ioaccval[3:0] x r/w 19-16 card1ioaccval[3:0] x r/w 15 enmcs3page x r/w 14 enmcs2page x r/w 13 enmcs1page x r/w 12 enmcs0page x r/w 11 encs3page x r/w 10 encs2page x r/w 9 encs1page x r/w 8 encs0page 0 r/w 7 card2waiten x r/w 6 card1waiten x r/w 5card2ioen x r/w 4card1ioen x r/w 3port8sel 0 r/w 2 port2_8sel 0 r/w 1 port1_8sel 0 r/w 0dclkdisable 0 r/w www.datasheet.in chapter 4 biu module 4-50 card2accval[3:0]: these bits define the access time for card 2 memory space. card1accval[3:0]: these bits define the access time for card 1 memory space. card2ioaccval[3:0]: these bits define the access time for card 2 io and attribute space. card1ioaccval[3:0]: these bits define the access time for card 1 io and attribute space. enmcs3page: setting this bit will enable read page mode for mcs3. enmcs2page: setting this bit will enable read page mode for mcs2. enmcs1page: setting this bit will enable read page mode for mcs1. enmcs0page: setting this bit will enable read page mode for mcs0. encs3page: setting this bit will enable read page mode for cs3. encs2page: setting this bit will enable read page mode for cs2. encs1page: setting this bit will enable read page mode for cs1. encs0page: setting this bit will enable read page mode for cs0. card2waiten: setting this bit will enable the card2wait* signal. card1waiten: setting this bit will enable the card1wait* signal. card2ioen: setting this bit will cause accesses to card 2 i/o space to assert the iord* or iowr* signals. this is used for accessing i/o cards. if this bit is not set, rd* or we* is asserted, which provides attribute space access. www.datasheet.in chapter 4 biu module 4-51 card1ioen: setting this bit will cause accesses to card 1 i/o space to assert the iord* or iowr* signals. this is used for accessing i/o cards. if this bit is not set, rd* or we* is asserted, which provides attribute space access. port8sel, port2_8sel, port1_8sel: these bits define the pcmcia port size. port8sel port2_8sel port1_8sel port1 port2 1 ** 8 bit port access 8 bit port access 0 0 1 8 bit port access 16 bit port access 0 1 0 16 bit port access 8 bit port access 0 1 1 8 bit port access 8 bit port access 0 0 0 16 bit port access 16 bit port access dclkdisable: setting this bit to 1 disables output of dclkout. clearing the bit to 0 enables output of dclkout except during memory power down (when memporwerdown bit is set to 1). 4.7.5 memory configuration 4 register offset = $010 bit label reset read/write 31 enbank1hdram 0 r/w 30 enbank0hdram 0 r/w 29 enarb 0 r/w 28 dissnoop 0 r/w 27 clrwrbuserrint 0 r/w 26 enbank1opt 0 r/w 25 enbank0opt 0 r/w 24 enwatch 0 r/w 23-20 watchtimeval[3:0] x r/w 19-17 reserved 16 mempowerdown 1 r/w 15 enrfsh1 0 r/w 14 enrfsh0 0 r/w 13-8 rfshval1[5:0] x r/w 7-6 reserved 5-0 rfshval0[5:0] x r/w enbank1hdram: setting this bit will enable the TMPR3911/12 to support hdram devices in memory bank 1. the bank1conf bits in the memory configuration 0 register will configure the tmpr3912 to support either a 16-bit hdram configuration or a 32-bit hdram configuration, in the same manner that standard dram is setup. www.datasheet.in chapter 4 biu module 4-52 enbank0hdram: setting this bit will enable the TMPR3911/12 to support hdram devices in memory bank 0. the bank0conf bits in the memory configuration 0 register will configure the TMPR3911/12 to support either a 16-bit hdram configuration or a 32-bit hdram configuration, in the same manner that standard dram is setup. enarb: setting this bit will always cause the cpu interface logic to externally arbitrate with the cpu during dma reads and writes when the dissnoop control bit is set. dissnoop: setting this bit will prevent the cpu interface logic from causing the snoop signal to assert to the cpu core during dma writes. clrwrbuserrint: wrbuserrint will occur whenever a write is timed out by the watch dog timer. this interrupt is connected directly to int[0] on the cpu and is completely independent of the rest of the TMPR3911/12 interrupt logic. when this interrupt is set, it will remain set until the clrwrbuserrint bit is asserted. the bit must be set and subsequently cleared to clear the interrupt. enbank1opt: setting this bit will cause the biu to insert an extra clock of delay between the assertion of ras1* and the assertion of the cas* signals for dram accesses. this is needed for interfacing to 80 ns drams when running with a clock greater than 70 mhz. enbank0opt: setting this bit will cause the biu to insert an extra clock of delay between the assertion of ras0* and the assertion of the cas* signals for dram accesses. this is needed for interfacing to 80 ns drams when running with a clock greater than 70 mhz. enwatch: setting this bit will enable the watch dog timer. watchtimeval[3:0]: these bits define the length of the watch dog timer. the watch dog timer rate is determined by the following equation: watch dog timer rate = f 64 1) 0] : [3 (watchtime clk * + mempowerdown: setting this bit will cause the memory interface to be put into memory power down mode which will cause the drams and sdrams to be put into self-refresh and all memory signals will be driven low. the memory interface will remain powered down until the processor attempts to access a location in memory other than function registers. www.datasheet.in chapter 4 biu module 4-53 enrfsh1: setting this bit will cause the biu to begin refreshing bank 1 drams or sdrams. this bit should not be set until meeting the start up specification requirements for the memory devices. enrfsh0: setting this bit will cause the biu to begin refreshing bank 0 drams or sdrams. this bit should not be set until meeting the start up specification requirements for the memory devices. rfshval1[5:0]: these bits define the refresh period for bank 1 refresh according to the following: $0 15.26 s $1 61.04 s $2 91.55 s $3 122.07 s rfshval0[5:0]: these bits define the refresh period for bank 0 refresh according to the following: $0 15.26 s $1 61.04 s $2 91.55 s $3 122.07 s : 4.7.6 memory configuration 5 register offset = $014: write-only bit label reset read/write 31-9 startval2[31:9] x w 8-4 reserved 3-0 mask2[3:0] x w startval2[31:9]: write-only these bits define the start address for re-map region 2. mask2[3:0]: write-only these bits define the mask for re-map region 2. www.datasheet.in chapter 4 biu module 4-54 4.7.7 memory configuration 6 register offset = $018: write-only bit label reset read/write 31-9 startval1[31:9] x w 8-4 reserved 3-0 mask1[3:0] x w startval1[31:9]: write-only these bits define the start address for re-map region 1. mask1[3:0]: write-only these bits define the mask for re-map region 1. 4.7.8 memory configuration 7 register offset = $01c: write-only bit label reset read/write 31-9 rmapadd2[31:9] x w 8-0 reserved rmapadd2[31:9]: write-only these bits define the destination address for re-map region 2. 4.7.9 memory configuration 8 register offset = $020: write-only bit label reset read/write 31-9 rmapadd1[31:9] x w 8-0 reserved rmapadd1[31:9]: write-only these bits define the destination address for re-map region 1. www.datasheet.in chapter 5 siu module 5-1 5. siu module 5.1 overview the siu module within the TMPR3911/12 provides the multi-channel 32-bit dma controller used to select and arbitrate the dma channels from each sim dma source. independent dma channels are provided for magicbus, video, sound, telecom, chi, uarta, and uartb sources. the siu module also contains the address decoder for all of the submodules contained within the sim. this decoder generates the read and write enable pulses for each of the internal function registers. www.datasheet.in chapter 5 siu module 5-2 5.2 implementation 5.2.1 block diagram priority encoder state machine and arbiter addr to memory data to memory sound dma ack video dma ack?s (burst of 4) magicbus dma ack start transaction signal rd/wr to memory magicbus dma data sound dma data telecom dma data chi dma data uarta dma data uartb dma data magicbus dma addr video dma addr sound dma addr telecom dma addr chi dma addr uarta dma addr uartb dma addr magicbus dma req & rd/wr video dma req & rd/wr sound dma req & rd/wr telecom dma req & rd/wr chi dma req & rd/wr uarta dma req & rd/wr uartb dma req & rd/wr lo pri hi pri data mux addr mux 4 selected dma source uartb dma ack uarta dma ack chi dma ack telecom dma ack 32 30 30 30 32 32 figure 5.2.1 siu dma controller block diagram www.datasheet.in chapter 5 siu module 5-3 5.2.2 dma controller description figure 5.2.1 shows a block diagram of the siu dma controller. the dma controller receives the dma requests and read/write status from all of the 7 possible dma sources (magicbus, video, sound, telecom, chi, uarta, and uartb) and uses a priority encoder to arbitrate and select the highest priority request. if a new request is received and the dma controller is currently busy, that request will remain pending and will be processed as soon as all other higher priority pending requests have been processed. the priority of the dma sources and the dma direction (read or write) supported are shown in table 5.2.1. table 5.2.1 dma sources dma source priority dma read (from memory) dma write (to memory) magicbus highest yes yes video (burst of 4 longs) yes no sound yes yes telecom yes yes chi yes yes uart-a (1 byte) yes yes uart-b (1 byte) lowest yes yes the state machine for the priority encoder also generates the start transaction pulse and read versus write status signal to the cpu interface for each dma transaction. after the arbiter decodes all received dma requests and selects the highest priority request as the dma channel to be processed, the dma address and data busses for the selected dma channel are routed to the memory subsystem. all dma sources transfer 1 word per transaction, except for the video which always transfers 4 consecutive words at a time (and thus returns 4 separate acks to the video module), and the uarts which transfer only 1 byte at a time. the uarts are thus tagged with the appropriate byte enable (corresponding to 1 of 4 byte positions) depending on the byte count in the dma address counter within the respective uart module. the state machine also generates the required acknowledge (ack) signal at the end of each dma transaction. this ack signal is used by the circuit corresponding to the respective dma source to either latch the data from memory (for a read transaction) or to enable the data to memory (for a write transaction). the siu also contains several test bits (see section 5.3) which allow detailed testing of the dma controller for various combinations of simultaneous dma requests. these bits are used for ic testing and should never be set. www.datasheet.in chapter 5 siu module 5-4 5.2.3 address decoder description figure 5.2.2 shows a block diagram of the sim address decoder. the address decoder generates the read and write enable pulses for each of the internal TMPR3911/12 control and status registers. the lower 8 bits of the internal address bus are decoded, along with the sim chip select and read/write status signal, to generate any 1 of 256 possible write enable pulses or any 1 of 256 possible read enable pulses. these enable pulses are used by the circuit/module targeted by the respective read or write pulse to either latch the data from the cpu (for a write transaction) or to enable the data to the cpu (for a read transaction). see the next section for a full listing of all the internal function registers, including their address offset and read versus write support. the address offset for function registers is the offset from the base address ($10c00000) of the function registers in the system address map. rd mem config 0 reg wr mem config 0 reg addr bus(9:2) rd/wr chip select sim address decoder rd mem config 1 reg wr mem config 1 reg rd mem config 2 reg wr mem config 2 reg rd chi holding reg wr chi holding reg 8 figure 5.2.2 sim address decoder block diagram www.datasheet.in chapter 5 siu module 5-5 5.2.4 internal function registers offset read/write register 000 r/w memory configuration 0 004 r/w memory configuration 1 008 r/w memory configuration 2 00c r/w memory configuration 3 010 r/w memory configuration 4 014 w memory configuration 5 018 w memory configuration 6 01c w memory configuration 7 020 w memory configuration 8 028 r/w video control 1 02c w video control 2 030 w video control 3 034 w video control 4 038 w video control 5 03c w video control 6 040 w video control 7 044 w video control 8 048 w video control 9 04c w video control 10 050 w video control 11 054 w video control 12 058 w video control 13 05c w video control 14 060 w sib size 064 w sib sound receive start 068 w sib sound transmit start 06c w sib tel receive start 070 w sib tel transmit start 074 r/w sib control 078 r/w sib sound holding register 07c r/w sib tel holding register 080 r/w sib sf0 control 084 r/w sib sf1 control 088 r sib sf0 status 08c r sib sf1 status 090 r/w sib dma control 0a0 r/w ir control 1 0a4 w ir control 2 0a8 w ir holding register 0b0 r/w uarta control 1 0b4 w uarta control 2 0b8 w uarta dma control 1 0bc w uarta dma control 2 0c0 r uarta dma count 0c4 r/w uarta holding register 0c8 r/w uartb control 1 0cc w uartb control 2 0d0 w uartb dma control 1 0d4 w uartb dma control 2 0d8 r uartb dma count 0dc r/w uartb holding register www.datasheet.in chapter 5 siu module 5-6 offset read/write register 0e0 r/w magicbus control 1 0e4 w magicbus control 2 0e8 w magicbus dma control 1 0ec w magicbus dma control 2 0f0 r magicbus dma control 0f4 w magicbus swap 0f8 r/w magicbus holding register 100 w clear interrupt 1 100 r interrupt status 1 104 w clear interrupt 2 104 r interrupt status 2 108 w clear interrupt 3 108 r interrupt status 3 10c w clear interrupt 4 10c r interrupt status 4 110 w clear interrupt 5 110 r interrupt status 5 114 r interrupt status 6 118 r/w enable interrupt 1 11c r/w enable interrupt 2 120 r/w enable interrupt 3 124 r/w enable interrupt 4 128 r/w enable interrupt 5 12c r/w enable interrupt 6 140 r rtc high 144 r rtc low 148 r/w alarm high 14c r/w alarm low 150 r/w timer control 154 r/w periodic timer 160 r/w spi control 164 r/w spi holding register 180 r/w io control 184 r/w multi-function io data out 188 r/w multi-function io direction 18c r multi-function io data in 190 r/w multi-function io select 194 r/w i/o power down 198 r/w multi-function i/o power down 1c0 r/w clock control 1c4 r/w power control 1c8 r/w siu test 1d8 r/w chi control 1dc r/w chi pointer enable 1e0 w chi receive pointer a 1e4 w chi receive pointer b 1e8 w chi transmit pointer a 1ec w chi transmit pointer b 1f0 r/w chi size 1f4 w chi receive start 1f8 w chi transmit start 1fc r/w chi holding register 208 r tx3911/12 revision register www.datasheet.in chapter 5 siu module 5-7 5.3 siu registers 5.3.1 siu test register offset = $1c8: bit label reset read/write 31-8 reserved 7 endmatest 0 r/w 6 ennotimetest 0 r/w 5-0 dmatestwr[5:0] 0 r/w endmatest: this bit is used for ic testing and should never be set. ennotimetest: this bit is used for ic testing and should never be set. dmatestwr[5:0]: these bits are used for ic testing and should never be set. 5.3.2 TMPR3911/12 revision register offset = $208: bit label reset read/write 31-8 reserved 7readrevision ? r readrevision: these bits indicate revisions of the TMPR3911/12. the following values are read out: tmpr3912au-92 : $01 tmpr3912xb-92 : $01 TMPR3911bu : $02 TMPR3911bxb : $02 www.datasheet.in chapter 5 siu module 5-8 www.datasheet.in chapter 6 clock module 6-1 6. clock module 6.1 overview the clock module within the TMPR3911/12 contains logic for generating the clocks for all other internal TMPR3911/12 modules, as well as for generating certain externally driven TMPR3911/12 output clocks. the clock module contains dividers for generating the correct rates for each clock and also contains logic for independently enabling or disabling individual clocks under software control. divmod in power control register in power module can be used to keep compatibility between TMPR3911 and tmpr3912 peripheral module, such as uart, timer and so on. because once divmod is set to high, peripheral master clock is generated by free clock, which means frequency of peripheral master clock is free of rf function. www.datasheet.in chapter 6 clock module 6-2 6.1.1 related pins sysclkin: input this pin should be connected along with sysclkout to an external crystal which is the main TMPR3911/12 clock source. sysclkout: output this pin should be connected along with sysclkin to an external crystal which is the main TMPR3911/12 clock source. www.datasheet.in chapter 6 clock module 6-3 6.2 implementation 6.2.1 block diagram irclk sibmclkdiv[2:0] chi master clock sysclk slowbus( * 2) rf[1:0]( * 1) osc pll ( 8) high rate clock enable logic sibmclkdir sibmclk sib interface coreclk clk2x clk enable clk mempowerdown reset freeclk xhfree prgm.divider envidclk mux mux divmod( * 4) video module vidclk prgm.divider ensibmclk sib master clock vidrf[1:0]( * 3) sibsclk sibsync chiclkdir chiclk prgm.divider enchimclk chiclkdiv[7:0] chi module chifs mux prgm.divider encserclk cserclkdiv[2:0] mux cserclk chimclksel csersel 1/2 or 1/4 ( * 6) ir module uarta module uartb module magic bus module uartaclk uartbclk enirclk enuartaclk enuartbclk 1/32 entimerclk 1/5 timer module spi module enspiclk magicbus master clock timer master clock spi master clock enmbusclk dclkdisable (*5) stopcpu dclkout 1/2 1/2 vcc3 figure 6.2.1 clock module block diagram www.datasheet.in chapter 6 clock module 6-4 rf[1:0] * 1 slowbus * 2 coreclk dclkout clk2x freeclk clk xhfree 00 0 f f f f f/2 f/2 01 0 f/2 f/2 f/2 f f/4 f/2 10 0 f/4 f/4 f/4 f f/8 f/2 11 0 f/8 f/8 f/8 f f/16 f/2 00 1 f/2 f/2 f/2 f f/4 f/2 01 1 f/4 f/4 f/4 f f/8 f/2 10 1 f/8 f/8 f/8 f f/16 f/2 11 1 f/16 f/16 f/16 f f/32 f/2 vidrf[1:0] * 3 vidclk 00 f/2 01 f/4 10 f/8 11 f/16 note: * 1 rf[1:0] is defined by the config register in tx39/h core. * 2 slowbus is defined by the power control register in power module. * 3 vidrf[1:0] is defined by the power control register in power module. * 4 divmod is defined by the power control register in power module. * 5 dclkdisable is defined by the memory configuration 3 register. * 6 1/2: tmpr3912xb-92/au-92 1/4: tmp3911bu/bxb www.datasheet.in chapter 6 clock module 6-5 6.2.2 clock module description figure 6.2.1 shows a block diagram of the clock module. the main TMPR3911/12 clock source is from an external crystal, connected to the TMPR3911/12 via the sysclkin/sysclkout pins. the TMPR3911/12 contains an oscillator which is internally connected to these pins. the output of the oscillator feeds a phase-locked-loop (or multiplier) circuit which takes the lower rate oscillator output and generates the higher-rate clocks required by the TMPR3911/12. for example, if the external sysclk crystal rate is 9.216 mhz, the pll multiplier circuit performs an 8 rate multiplication to generate a high-speed clock rate of 73.728 mhz. each of the individual clocks can also be enabled or disabled under software control, in order to reduce power consumption. all of these clocks default to a disabled state during reset. the main high rate clocks generated by the clock module are the following: ? clk2x ? variable rate clock and same rate as the coreclk; used for generating other lower rate clocks and for certain memory interface circuits in the biu ? clk ? half rate of clk2x used as the master clock for many of the TMPR3911/12 modules and for generating other lower rate clocks ? coreclk ? same rate as clk2x and twice the rate of clk (TMPR3911/12); used as master clock for cpu core. ? dclkout ? same rate as clk2x; used as high-speed externally driven clock for sdrams ? freeclk ? fixed rate clock generated by pll ? xhfree ? half rate of freeclk ? the sibmclk pin can be configured as an output, for which the programmable rate is generated by dividing down from clk2x. the sibmclk pin can also be configured as an input. in this mode, all sib clocks are derived from an external sibmclk oscillator source, which is asynchronous with respect to clk2x. this mode allows optional decoupling of the sib (as well as the chi and uart) rates from the cpu core clock rate. the selected sibmclk source is then used as the sib master clock for the sib module circuits, and is also used to generate the sibsclk and sibsync externally driven TMPR3911/12 output signals. ? the chiclk pin can be configured as an output, for which the programmable rate is generated by dividing down from either clk or the sib master clock. the chiclk pin can also be configured as an input. in this mode, all chi clocks are derived from an external peripheral source and the chi module will slave to this external clock. the selected chiclk source is used as the chi master clock for the chi module circuits, and is also used to generate the chifs externally driven TMPR3911/12 output signal. ? the programmable uart master clock is generated by dividing down from either clk or the sib master clock, and is used as the master clock for the baud generator circuit within each uart module. ? the clock module also contains several fixed dividers for generating the master clocks for the video, magicbus, rtc timer, and spi circuits. these clocks are divided down from either clk2x or clk. www.datasheet.in chapter 6 clock module 6-6 6.3 clock registers 6.3.1 clock control register offset = $1c0: bit label reset read/write 31-24 chiclkdiv[7:0] 0 r/w 23 reserved * 0 ? 22 reserved * 0 ? 21 chimclksel 0 r/w 20 chiclkdir 0 r/w 19 enchimclk 0 r/w 18 envidclk 0 r/w 17 enmbusclk 0 r/w 16 enspiclk 0 r/w 15 entimerclk 0 r/w 14 reserved * 0 ? 13 sibmclkdir 0 r/w 12 reserved 0 ? 11 ensibmclk 0 r/w 10-8 sibmclkdiv[2:0] 0 r/w 7csersel 1 r/w 6-4 cserdiv[2:0] 0 r/w 3 encserclk 0 r/w 2 enirclk 0 r/w 1 enuartaclk 0 r/w 0 enuartbclk 0 r/w * ) these bits must be zero. chiclkdiv[7:0]: these bits define the divide-modulus for the programmable divider used to generate chiclk. the divide-modulus is equal to (chiclkdiv+2). (see the following table.) chiclkdiv[7:0] divide-modulus 02 13 24 nn+2 253 255 254 256 ? ? ? ? www.datasheet.in chapter 6 clock module 6-7 chimclksel: setting this bit to a logic ?1? selects the external sibmclk source to be the chi master clock. clearing this bit to a logic ?0? selects an internal clock source to be the chi master clock. chiclkdir: this bit controls the direction of the chiclk pin. setting this bit to a logic ?1? configures chiclk to be an output (chi master mode). clearing this bit to a logic ?0? configures chiclk to be an input (chi slave mode). enchimclk: this bit is used to enable or disable the chiclk counter and chiclk clock generation. setting this bit to a logic ?1? enables the chiclk counter and chiclk generation. clearing this bit to a logic ?0? disables the chiclk counter and chiclk generation, halting the clock to the chi module in order to reduce power consumption. envidclk: this bit is used to enable or disable the video master clock. setting this bit to a logic ?1? enables the vidclk. clearing this bit to a logic ?0? disables the vidclk, halting the clock to the video module in order to reduce power consumption. enmbusclk: this bit is used to enable or disable the magicbus master clock. setting this bit to a logic ?1? enables the magicbus master clock. clearing this bit to a logic ?0? disables the magicbus master clock, halting the clock to the magicbus module in order to reduce power consumption. enspiclk: this bit is used to enable or disable the spiclk counter and spi master clock generation. setting this bit to a logic ?1? enables the spiclk counter and spi master clock generation. clearing this bit to a logic ?0? disables the spiclk counter and spi master clock generation, halting the clock to the spi module in order to reduce power consumption. entimerclk: this bit is used to enable or disable the rtc periodic timer clock counter. setting this bit to a logic ?1? enables the timer clock counter. clearing this bit to a logic ?0? disables the timer clock counter. sibmclkdir: this bit controls the direction of the sibmclk pin. setting this bit to a logic ?1? configures sibmclk to be an output. clearing this bit to a logic ?0? configures sibmclk to be an input. ensibmclk: this bit is used to enable or disable the sibmclk counter and sibmclk clock generation. setting this bit to a logic ?1? enables the sibmclk counter and sibmclk generation. clearing this bit to a logic ?0? disables the sibmclk counter and sibmclk generation, halting the clock to the sib module in order to reduce power consumption. www.datasheet.in chapter 6 clock module 6-8 sibmclkdiv[2:0]: these bits define the divide-modulus for the programmable divider used to generate sibmclk. the divide-modulus is equal to (sibmclk+2). (see the following table.) sibmclkdiv divide-modulus 02 13 24 35 46 57 68 csersel: clearing this bit to a logic ?0? selects the external sibmclk source to be the cserclk master clock. setting this bit to a logic ?1? selects an internal clock source to be the cserclk master clock. cserdiv[2:0]: these bits define the divide-modulus for the programmable divider used to generate cserclk. the divide-modulus is equal to (cserdiv+2). (see the following table.) cserdiv divide-modulus 02 13 24 35 46 57 68 encserclk: this bit is used to enable or disable the cserclk counter. setting this bit to a logic ?1? enables the cserclk counter. clearing this bit to a logic ?0? disables the cserclk counter. enirclk: this bit is used to enable or disable the irclk clock generation. setting this bit to a logic ?1? enables the irclk generation. clearing this bit to a logic ?0? disables the irclk generation, halting the clock to the ir module in order to reduce power consumption. enuartaclk: this bit is used to enable or disable the uartaclk clock generation. setting this bit to a logic ?1? enables the uartaclk generation. clearing this bit to a logic ?0? disables the uartaclk generation, halting the clock to the uarta module in order to reduce power consumption. enuartbclk: this bit is used to enable or disable the uartbclk clock generation. setting this bit to a logic ?1? enables the uartbclk generation. clearing this bit to a logic ?0? disables the uartbclk generation, halting the clock to the uartb module in order to reduce power consumption. www.datasheet.in chapter 6 clock module 6-9 table 6.3.1 through table 6.3.3 show examples of the frequencies for each clock. table 6.3.1 clock frequencies (1) divmod = 0, chimclksel = 0, csersel = 1, rf[1:0] = 00, slowbus = 0 frequency clock symbol calculation register setting value frequency (mhz) sysclk (external crystal) f in ? 7.3728 9.216 11.520 dclkout (sdram clock) f dclkout f in 8 58.9824 73.728 92.160 clk f clk f in 4 29.4912 36.864 46.080 clk2x f clk2x f in 8 58.9824 73.728 92.160 xhfree f xhfree f in 4 29.4912 36.864 46.080 freeclk f freeclk f in 8 58.9824 73.728 92.160 vidclk (video master clock) f vidclk f xhfree (2^vidrf[1:0]) vidrf = 00 01 10 11 29.4912 14.7456 7.3728 3.6864 36.864 18.432 9.216 4.608 46.080 23.040 11.520 5.760 sibmclk (sib master clock) f sibmclk f clk2x (sibmclkdiv[2:0] + 2) sibmclkdiv = 000 001 010 011 100 101 110 111 29.4912 19.6608 14.7456 11.7965 9.8304 8.4261 7.3728 ? 36.864 24.576 18.432 14.746 12.288 10.532 9.216 ? 46.080 30.720 23.040 18.432 15.360 13.166 11.520 ? chiclk (chi clock) f chiclk f clk (chiclkdiv[7:0] + 2) chiclkdiv = $00 $fe 14.7456 0.1152 18.432 0.144 23.040 0.180 f clk2x 4 (3911bu/bxb) 14.7456 18.432 ? cserclk f cserclk f clk2x 2 (au-92/xb-92) ? ? 46.08 irclk (ir master clock) f irclk f cserclk (cserdiv[2:0] + 2) uartaclk (uart-a master clock) f uartaclk f cserclk (cserdiv[2:0] + 2) uartbclk (uart-b master clock) f uartbclk f cserclk (cserdiv[2:0] + 2) cserdiv = 000 001 010 011 100 101 110 111 7.3728 4.9152 3.6864 2.94912 2.4576 2.1065 1.8432 ? 9.216 6.144 4.608 3.6864 3.072 2.633 2.304 ? 23.04 15.36 11.52 9.216 7.680 6.5829 5.760 ? mbusmclk (magic bus master clock) f mbusmclk f clk 29.4912 36.864 46.089 timerclk (timer master clock) f timerclk f clk 32 0.9216 1.152 1.440 spimclk (spi master clock) f spimclk f clk 5 5.8982 7.3728 9.216 sysclk (external crystal) f in ? 7.3728 9.216 11.520 dclkout (sdram clock) f dclkout f in 4 29.4912 36.864 46.080 clk f clk f in 2 14.7456 18.432 23.040 clk2x f clk2x f in 4 29.4912 36.864 46.080 www.datasheet.in chapter 6 clock module 6-10 table 6.3.2 clock frequencies (2) divmod = 0, chimclksel = 0, csersel = 1, rf[1:0] = 01, slowbus = 0 or rf[1:0] = 00, slowbus = 1 frequency clock symbol calculation register setting value frequency (mhz) xhfree f xhfree f in 4 29.4912 36.864 46.080 freeclk f freeclk f in 8 58.9824 73.728 92.160 vidclk (video master clock) f vidclk f xhfree (2^vidrf[1:0]) vidrf = 00 01 10 11 29.4912 14.7456 7.3728 3.6864 36.864 18.432 9.216 4.608 46.080 23.040 11.520 5.760 sibmclk (sib master clock) f sibmclk f clk2x (sibmclkdiv[2:0] + 2) sibmclkdiv = 000 001 010 011 100 101 110 111 14.7456 9.8304 7.3728 5.8982 4.9152 4.2130 3.6864 ? 18.432 12.288 9.216 7.373 6.144 5.266 4.608 ? 23.040 15.360 11.520 9.216 7.680 6.583 5.760 ? chiclk (chi clock) f chiclk f clk (chiclkdiv[7:0] + 2) chiclkdiv = $00 $fe 7.3728 0.0576 9.216 0.072 11.520 0.090 cserclk f cserclk f clk2x 4 (3911bu/bxb) 7.3728 9.216 ? f clk2x 2 (au-92/xb-92) ? ? 23.040 irclk (ir master clock) f irclk f cserclk (cserdiv[2:0] + 2) cserdiv = 000 001 010 011 100 101 110 111 3.6864 2.4576 1.8432 1.4746 1.2288 1.0533 0.9216 ? 4.608 3.072 2.304 1.8432 1.536 1.3165 1.152 ? 11.52 7.68 5.76 4.608 3.840 3.291 2.880 ? f cserclk (cserdiv[2:0] + 2) f cserclk (cserdiv[2:0] + 2) uartaclk (uart-a master clock) uartbclk (uart-b master clock) mbusmclk (magic bus master clock) f uartaclk f uartbclk f mbusmclk f clk 14.7456 18.432 23.040 timerclk (timer master clock) f timerclk f clk 32 spimclk (spi master clock) f spimclk f clk 5 sysclk (external crystal) f in ? 0.4608 2.9491 0.576 3.6864 0.720 4.608 dclkout (sdram clock) f dclkout f in 4 29.4912 36.864 46.080 clk f clk f in 2 14.7456 18.432 23.040 clk2x f clk2x f in 4 29.4912 36.864 46.080 xhfree f xhfree f in 4 29.4912 36.864 46.080 freeclk f freeclk f in 8 58.9824 73.728 92.160 www.datasheet.in chapter 6 clock module 6-11 table 6.3.3 clock frequencies (3) divmod = 1, chimclksel = 0, csersel = 1, rf[1:0] = 01, slowbus = 0 or rf[1:0] = 00, slowbus = 1 frequency clock symbol calculation register setting value frequency (mhz) vidclk (video master clock) f vidclk f xhfree (2^vidrf[1:0]) vidrf = 00 01 10 11 29.4912 14.7456 7.3728 3.6864 36.864 18.432 9.216 4.608 46.080 23.040 11.520 5.760 sibmclk (sib master clock) f sibmclk f freeclk (sibmclkdiv[2:0] + 2) sibmclkdiv = 000 001 010 011 100 101 110 111 29.4912 19.6608 14.7456 11.7965 9.8304 8.4261 7.3728 ? 36.864 24.576 18.432 14.746 12.288 10.532 9.216 ? 46.080 30.720 23.040 18.432 15.360 13.166 11.520 ? chiclk (chi clock) f chiclk f xhfree (chiclkdiv[7:0] + 2) chiclkdiv = $00 $fe 14.7456 0.1152 18.432 0.144 23.040 0.180 f freeclk 4 (3911bu/bxb) 14.7456 18.432 ? cserclk f cserclk f freeclk 2 (au-92/xb-92) ? ? 46.08 irclk (ir master clock) f irclk f cserclk (cserdiv[2:0] + 2) uartaclk (uart-a master clock) f uartaclk f cserclk (cserdiv[2:0] + 2) uartbclk (uart-b master clock) f uartbclk f cserclk (cserdiv[2:0] + 2) cserdiv = 000 001 010 011 100 101 110 111 7.3728 4.9152 3.6864 2.94912 2.4576 2.1065 1.8432 ? 9.216 6.144 4.608 3.6864 3.072 2.633 2.304 ? 23.04 15.36 11.52 9.216 7.680 6.5829 5.760 ? mbusmclk (magic bus master clock) f mbusmclk f xhfree 29.4912 36.864 46.089 timerclk (timer master clock) f timerclk f xhfree 32 0.9216 1.152 1.440 spimclk (spi master clock) f spimclk f xhfree 5 5.8982 7.3728 9.216 www.datasheet.in chapter 6 clock module 6-12 www.datasheet.in chapter 7 chi module 7-1 7. chi module 7.1 overview the chi module within the TMPR3911/12 contains holding registers, shift registers, dma support, and other logic to support interfacing to external full-duplex serial tdm communication peripherals, including isdn communication devices and pcm/tdm serial highways. the TMPR3911/12 implementation of the chi module is based on the concentration highway interface standard specified by intel and at&t, which is intended to allow glueless interface to various tdm highways used by numerous commercial products. the TMPR3911/12 chi module can also be used to support an intra-system high-speed serial dma channel within a pic system. the TMPR3911/12 chi module utilizes a 4-signal interface consisting of clock, sync, transmit serial data, and receive serial data. the data is organized as a tdm format, with up to 64 timeslots (nominally 8 bits each) per frame, with a nominal frame rate of 8 khz (8 bits 8 khz = 64 kbps nominal data rate per channel). up to four input timeslots and up to four output timeslots can be independently selected in each half-frame. the chi module does not handle the timeslots which are not selected for input or output. the number of timeslots and the data rate (up to 4.096 mbps) and frame rate (up to 64 khz, depending on the system configuration) are programmable, providing flexibility for supporting various tdm communication peripherals. these timeslots are commonly used to carry voice, data, or control and status information. the chi module provides full-duplex dma support for receive and transmit (two dma channels). the dma buffers can be configured in a continuous (circular) buffer mode or a one-time (empty or fill, then stop) buffer mode. half-buffer and end-of-buffer dma address counter interrupts are available, allowing the cpu to minimize overhead and efficiently empty or fill half of the dma buffer in a ping-pong fashion. the dma buffer size is programmable (up to a maximum of 16 kbytes) and the receive and transmit buffers can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). also available is a direct cpu read/write mode for bypassing the dma, allowing the cpu to read or write the chi data on a sample by sample basis, if so desired. 7.1.1 related pins chifs: input/output this pin is the chi frame synchronization signal. this pin is available for use in one of two modes. as an output, this pin allows the TMPR3911/12 to be the master chi sync source. as an input, this pin allows an external peripheral to be the master chi sync source and the TMPR3911/12 chi module will slave to this external sync. chiclk: input/output this pin is the chi clock signal. this pin is available for use in one of two modes. as an output, this pin allows the TMPR3911/12 to be the master chi clock source. as an input, this pin allows an external peripheral to be the master chi clock source and the TMPR3911/12 chi module will slave to this external clock. chidout: output this pin is the chi serial data output signal. chidin: input this pin is the chi serial data input signal. www.datasheet.in chapter 7 chi module 7-2 7.2 interface requirements 7.2.1 frame structure and serial timing each chi frame (nominally 8 khz rate) is time-division-multiplexed into several timeslots or channels. the total number of timeslots per frame is programmable, with a maximum of 64 timeslots allowed, and the number of timeslots is also restricted to an even number. each timeslot is 8 bits, although 16-bit or 32-bit channels can be supported by accessing adjacent timeslots. the TMPR3911/12 chi module supports a master or slave mode for both the clock (chiclk) and sync (chifs). for the master mode, the TMPR3911/12 contains programmable dividers for generating the clock and/or sync signal, synchronously dividing down from the main core clock (clk). for the slave mode, TMPR3911/12 accepts external clock and/or sync signals and utilizes ?digital-pll? type circuitry to stayed ?locked? to the external source. the chi module supports the following programmable features which allow support for various clock and sync timing formats: ? 1x versus 2x clock modes for chiclk (2x clock mode uses two chiclk periods per data bit) ? msb-first versus lsb-first serial formats for transmit and receive ? rising versus falling edge (polarity) used for frame sync triggering ? chifs signal can be sampled on either rising or falling edge of chiclk ? chidin receive data can be sampled on either rising or falling edge of chiclk ? chidout transmit data can be pushed on either rising or falling edge of chiclk ? chidin receive data can have programmable bit offset (timeslot 0 offset from chifs) ? chidout transmit data can have programmable bit offset (timeslot 0 offset from chifs) ? chidout transmit data (tri-state) output buffer enable is dynamically asserted for only active timeslots; for sleep mode chidout is always tri-stated ? for chifs master mode, the chifs pulse width and polarity is programmable the TMPR3911/12 chi module allows for a programmable bit offset for both chidin and chidout, which is related to the number of clock cycles between the start of timeslot 0 and chifs. this flexibility allows the TMPR3911/12 chi module to support a wide variety of interface clock and sync timing formats. the control bits for controlling the chidin bit offset are chirxboff[3:0], while the control bits for controlling the chidout bit offset are chitxboff[3:0]. www.datasheet.in chapter 7 chi module 7-3 table 7.2.1 and table 7.2.2 shows a summary matrix for the values of cerx and cetx for all possible settings of chirxboff and chitxboff, respectively. these values are shown for various configurations of chiclk mode (1x versus 2x), chifsedge, chirxedge, and chitxedge. the chifsedge settings determine whether to use the rising edge (chifsedge = 1) or falling edge (chifsedge = 0) of chiclk to sample chifs. the chirxedge settings determine whether to use the rising edge (chirxedge = 1) or falling edge (chirxedge = 0) of chiclk to sample the chidin input. the chitxedge settings determine whether to use the rising edge (chitxedge = 1) or falling edge (chitxedge = 0) of chiclk to push the chidout output. cerx is defined as the number of chiclk clock edges (rising and falling) between the edge where chifs is sampled and the edge where chidin is sampled. cetx is defined as the number of chiclk clock edges (rising and falling) between the edge where chifs is sampled and the edge where chidout is pushed. the chi frame structure and bit offsets are shown in figure 7.2.1~7.2.7 for various clock and sync configurations. table 7.2.1 cerx values for chirxboff versus clock and edge configurations chirxboff chiclk mode chifs- edge chirx- edge 0123456789101112131415 1x 0 0 0 2 4 6 8 1012141618202224262830 1x 1 1 0 2 4 6 8 1012141618202224262830 1x 0 1 -1 1 3 5 7 9 11131517192123252729 1x 1 0 -1 1 3 5 7 9 11131517192123252729 2x 0 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 2x 1 1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 2x 0 1 1 3 5 7 9 1113151719212325272931 2x 1 0 1 3 5 7 9 1113151719212325272931 table 7.2.2 cetx values for chitxboff versus clock and edge configurations chitxboff chiclk mode chifs- edge chitx- edge 0123456789101112131415 1x 0 0 0 2 4 6 8 1012141618202224262830 1x 1 1 0 2 4 6 8 1012141618202224262830 1x 0 1 -1 1 3 5 7 9 11131517192123252729 1x 1 0 -1 1 3 5 7 9 11131517192123252729 2x 0 0 0 2 4 6 8 1012141618202224262830 2x 1 1 0 2 4 6 8 1012141618202224262830 2x 0 1 -1 1 3 5 7 9 11131517192123252729 2x 1 0 -1 1 3 5 7 9 11131517192123252729 when the chi frame consists of only two time slots, not all the boff values are supported. the offsets must be within the half-frame. www.datasheet.in chapter 7 chi module 7-4 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.1 chi frame structure example chiclk 1x mode chifs sampled on falling edge chidin sampled on falling edge; rxboff = 0; cerx = 0 chidout pushed on rising edge; txboff = 0; cetx = ? 1 chiclk chidout chidin chifs channel 63 channel 1 7 6 2 1 0 channel 0 frame start channel 1 start 7 6 2 1 0 figure 7.2.2 chi frame structure example chiclk 1x mode chifs sampled on rising edge chidin sampled on falling edge; rxboff = 1; cerx = 1 chidout pushed on falling edge; txboff = 1; cetx = 1 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.3 chi frame structure example chiclk 1x mode chifs sampled on falling edge chidin sampled on rising edge; rxboff = 2; cerx = 3 chidout pushed on falling edge; txboff = 0; cetx = 0 www.datasheet.in chapter 7 chi module 7-5 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.4 chi frame structure example chiclk 2x mode chifs sampled on falling edge chidin sampled on rising edge; rxboff = 0; cerx = 1 chidout pushed on rising edge; txboff = 0; cetx = ? 1 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.5 chi frame structure example chiclk 2x mode chifs sampled on falling edge chidin sampled on rising edge; rxboff = 2; cerx = 5 chidout pushed on rising edge; txboff = 2; cetx = 3 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.6 chi frame structure example chiclk 2x mode chifs sampled on rising edge chidin sampled on rising edge; rxboff = 0; cerx = 2 chidout pushed on rising edge; txboff = 0; cetx = 0 www.datasheet.in chapter 7 chi module 7-6 chiclk chidout chidin chifs channel 63 channel 1 channel 0 frame start channel 1 start 7 6 2 1 0 7 6 2 1 0 figure 7.2.7 chi frame structure example chiclk 2x mode chifs sampled on falling edge chirxfspol = 1 (negative polarity) chidin sampled on rising edge; rxboff = 1; cerx = 3 chidout pushed on rising edge; txboff = 1; cetx = 1 www.datasheet.in chapter 7 chi module 7-7 7.2.2 configurations the programmability of the clock, sync, bit offsets, and number of timeslots allows the chi module to support a wide range of configurations. several of these configurations are commonly utilized as communication interfaces by numerous commercial products, some of which are briefly discussed below. other configurations are available for application-specific usage. the k2 interface is an at&t standard used as a serial inter-chip digital interface between u-interface transmission circuits and various system-wide interface circuits. the k2 interface utilizes four pins (clock, sync, data in, and data out) and consists of eight 8-bit timeslots, with a frame rate of 8 khz and a clock rate of 512 khz. the sld interface utilizes 3 pins (clock, sync, data), with the transmit and receive pins tied together, such that the data is sent bi-directionally in a ping-pong fashion. the sld interface consists of eight 8- bit timeslots, with 4 timeslots reserved for transmit and 4 timeslots reserved for receive. the frame rate is 8 khz and the clock rate is 512 khz. the gci interface is a 4-pin variable-speed tdm highway utilizing anywhere from 4 to 48 timeslots. the frame rate is 8 khz and the clock rate is 2x the data rate and varies from 512-khz to 6.144 mhz. the iom-2 interface is commonly used to interface to 4-pin isdn line interface drivers. each frame consists of twelve 8-bit timeslots, with a frame rate of 8 khz and a (2x) clock rate of 1.536-mhz. the cept level-1 pcm format is a common communications standard used for digital transmission of voice and data. each frame consists of 32 8-bit timeslots, with a frame rate of 8-khz and a (1x) clock rate of 2.048 mhz. table 7.2.3 shows a summary matrix of several example chi configurations and their associated parameters. table 7.2.3 example chi configurations (table values based on clk = 36.864 mhz) chiclk divide time slots chiclk mode fs chiclk rate data rate comments 4.5 64 2x 8 khz 8.192 mhz 4.096 mbps slave mode only 6 48 2x 8 khz 6.144 mhz 3.072 mbps gci format 9 64 1x 8 khz 4.096 mhz 4.096 mbps chi format 9 8 1x 64 khz 4.096 mhz 4.096 mbps hi-speed mode 10 64 1x 7.2 khz 3.6864 mhz 3.6864 mbps 12 24 2x 8 khz 3.072 mhz 1.536 mbps 12 48 1x 8 khz 3.072 mhz 3.072 mbps 18 32 1x 8 khz 2.048 mhz 2.048 mbps cept pcm format 24 12 2x 8 khz 1.536 mhz 768 kbps iom-2 format 72 8 1x 8 khz 512 mhz 512 kbps k2, sld formats note that the maximum achievable frame rate depends on the system configuration. if devices with long access time and/or 16 bit-wide data bus are used, the frame rate of 64 khz may be unachievable because of the reduced bus band width. using other interfaces in parallel with chi and/or reducing the cpu clock frequencies will also reduce the band width available for chi. www.datasheet.in chapter 7 chi module 7-8 7.3 implementation 7.3.1 block diagram control from cpu msb vs lsb first clock and control logic 8b tx shift reg rx hold load chiclk chifs chidout txoe data from dma or cpu 32b tx hold reg-b chidin data to dma or cpu clk cmp cmp rx ch cnt tx shift load tx ch cnt chi ctrl and stat reg tx tdm switch ctrl reg synch prgm divider out reg 8 32 32 8 8 8 32b tx hold reg-a rx tdm switch ctrl reg 8b rx shift reg msb vs lsb first 32b rx hold reg-b 32b rx hold reg-a prgm divider synch synch figure 7.3.1 chi module block diagram the chi module consists of holding registers (both transmit and receive), shift registers (both transmit and receive), dma support, and other logic to support interfacing to various types of tdm highways. see figure 7.3.1 for a block diagram of the chi module. www.datasheet.in chapter 7 chi module 7-9 7.3.2 transmitter for the chi transmit direction, buffer-a and buffer-b transmit holding registers are written either from the dma circuit or directly from the cpu. each of these 2 holding registers are 32-bits wide, and chi control logic determines which byte from which holding register gets loaded at a given time into the 8-bit transmit shift register. in addition, the byte data loaded from the holding register to the shift register can be msb-first or lsb-first. the reason for having buffer-a and buffer-b holding registers is that the chi module operates in a ping-pong fashion. each frame of data is partitioned into 2 buffers (a and b); for example, with 64 timeslots total, the data is partitioned into 32 timeslots per buffer. the ping-pong operation allows one buffer to be updated (via the dma or cpu) while the other buffer is being loaded into the shift register a byte at a time, depending on which timeslots are active. the ping- pong operation is transparent to the cpu or dma interface, since the chi module automatically points to the correct a or b buffer at a given time and the cpu or dma always accesses the same 32-bit holding register for all transactions. the transmit tdm switch control register is used to select any 4 channels per buffer to be loaded from the holding register to the shift register. for example, if the chi module is configured for 32 timeslots per buffer (64 total timeslots), any 4 channels per buffer (8 total) can be selected out of the 32 available channels. the chidout signal is tri-stated during any of the non-selected channels. each of the 8 selected channels also has an individual control bit for enabling/disabling the timeslot. figure 7.3.2 shows how the transmit tdm switch works, for example, with 16 total timeslots. byte3 byte2 byte1 byte0 tx holding register a bit31????????.bit0 byte3 byte2 byte1 byte0 tx holding register b bit31????????.bit0 ch0 ch1 ch2 ch3 hi-z hi-z hi-z hi-z hi-z ch9 hi-z ch11 hi-z ch13 ch14 hi-z bit0??????.bit31 bit 16?13 8?15 24?31 0?7 chinchan[4:0] txmsbfirst chi pointer enable chi transmit pointer a chi transmit pointer b 0x07 0 0xffxx0000 0x03020100 0x05010306 chidout chifs figure 7.3.2 transmit tdm switch example 7.3.3 receiver for the chi receive direction, buffer-a and buffer-b receive holding registers are read either by the dma circuit or directly by the cpu. each of these 2 holding registers are 32 bits wide, and chi control logic determines which byte to which holding register gets loaded at a given time from the 8-bit receive shift register. in addition, the byte data loaded from the shift register to the holding register can be msb-first or lsb-first. similar to the transmit direction, the receive section also operates in a ping- pong fashion, allowing one buffer to be read (via the dma or cpu) while the other buffer is being loaded from the shift register a byte at a time, depending on which timeslots are active. the receive tdm switch control register (independent from the transmit tdm switch control register) is used to select any 4 channels per buffer to be loaded from the shift register to the holding register. each of the 8 selected channels also has an individual control bit for enabling/disabling the timeslot. www.datasheet.in chapter 7 chi module 7-10 an interrupt is available whenever a valid 32 bit word is available from the receive data holding register a. this also means a valid chi output sample can be written to the transmit data holding register a. similarly, an interrupt is also available whenever a valid 32 bit word is available from the receive data holding register b. this also means a valid chi output sample can be written to the transmit data holding register b. 7.3.4 clock and control generation the chi module contains several programmable counters which are used to generate the various chi internal and external control signals and clocks. see figure 7.3.3 for a block diagram of the chi clock and control generation circuit. as mentioned previously, chiclk can be configured as either an output (master mode) or input (slave mode). as an output, chiclk is derived by dividing down from clk. in this mode, all chi clocks are then synchronously locked to the main TMPR3911/12 system clock. as an input, chiclk is generated from an external clock source, which is asynchronous with respect to clk. the TMPR3911/12 chi module utilizes a digital-pll circuit to stay ?locked? to the external source, while still operating internally using clk. chidin and chidout are also synchronized between clk and the externally-supplied chiclk. chifs can also be configured as either an output (master mode) or input (slave mode). as an output, chifs is derived by dividing down from chiclk. for this mode, the chifs pulse width and polarity is also programmable. as an input, chifs is generated from an external sync source. the TMPR3911/12 chi module utilizes a digital-pll circuit to stay ?locked? to the external sync source, while still operating internally using clk. the programmable receive and transmit sync delay counters shown in figure 7.3.3 are used to implement the bit offset feature described earlier. the bit offset control bits determine the number of clock cycles between the start of timeslot 0 and chifs. the receive and transmit sync delay counters are independent from each other, such that the receive and transmit serial data streams can have different bit offsets. the programmable receive channel counter output is constantly compared with the receive tdm switch control register values, and whenever a match occurs, the byte of data is loaded from the receive shift register into the correct field within the receive holding register. similarly, the programmable transmit channel counter output is constantly compared with the transmit tdm switch control register values, and whenever a match occurs, the byte of data is loaded from the correct field within the transmit holding register into the receive shift register. all control registers, including the tdm switch control registers, must be unchanged while the chi module is enabled. if any register is changed during the chi operation, the result is undefined. www.datasheet.in chapter 7 chi module 7-11 prgm tx fs delay cnt prgm rx chan cnt 8/16 rx bit cnt prgm rx fs delay cnt prgm chifs divider prgm chiclk divider cmp decode rx start/stop control rx shift reg control rx holding reg control rx dma req control sample interrupt rx tdm switch cntl chifs clk chiclk synch digital pll synch digital pll prgm tx chan cnt 8/16 tx bit cnt control from cpu decode tx start/stop control tx shift reg control tx holding reg control tx dma req control sample interrupt tx chidout enable tx tdm switch cntl cmp figure 7.3.3 chi clock and control generation www.datasheet.in chapter 7 chi module 7-12 7.3.5 dma address generation the chi module provides support for 2 full-duplex dma channels: receive and transmit. the circuit used to generate the dma address, as well as half-buffer and end-of-buffer interrupts is shown in figure 7.3.4. 12 30 12 12 half-buffer interrupt one-time vs. circular mode end-of-buffer interrupt dma control from cpu dma addr rx start addr dma rd/wr mode clk 30 tx start addr 2:1 dma cntl reg cnt load logic buffer size cmp cmp addr cnt 2 figure 7.3.4 chi dma address generation www.datasheet.in chapter 7 chi module 7-13 the dma buffer size is programmable (up to a maximum of 16 kbytes) and the receive and transmit buffer start addresses are also programmable (anywhere over the full 32-bit address space). because there are separate start addresses, the receive and transmit buffers can be configured to either reside in different memory spaces or share the same memory space. the latter setup allows for overlapping buffers for loopback purposes or for optimum memory allocation, for which the dma logic supports two full-duplex loopback modes. for one mode, receive dma requests are issued first, followed by transmit dma requests. this ordering allows a receive-to-transmit immediate loopback via the dma buffer. for the second mode, transmit dma requests are issued first, followed by receive dma requests. thus, received samples are written to the dma buffer location immediately after transmit samples were read from that same location (which then became immediately available). this ordering allows a single circular dma buffer to be used for both transmit and receive samples. the dma buffers can be configured in a circular buffer mode or a one-time buffer mode. for the circular mode, the dma address is continuously incremented (each time a dma acknowledge is received from the TMPR3911/12?s central dma controller) and rolls over back to the start address after the end-of-buffer is reached and will continue operating in a continuous and circular manner. for the one-time mode, the dma logic will stop executing whenever the end-of-buffer is reached. because the chi module reads and writes a byte at a time between the shift registers and the 32 bit holding registers, the software must pack and unpack these bytes to and from the 32 bit words in memory in order to multiplex and demultiplex each channel for processing. table 7.3.1 shows the format and organization of the chi channels within memory for dma mode. consecutive byte samples for a given channel reside in memory every 8th byte. note that the byte lanes are swapped between the little- and big-endian modes. in the little-endian mode, bits 31:24 of a word on the dma buffer correspond to the byte lane with the address offset ?+3? and therefore to the ?byte0? in the chi tx/rx holding register. on the contrary, in the big-endian mode, bits 31:24 of a word on the dma buffer correspond to the byte lane with the address offset ?+0? and therefore to the ?byte3? in the chi tx/rx holding register. table 7.3.1 chi dma memory organization (relative) memory address +0 +1 +2 +3 +0x0 buffa, byte3 buffa, byte2 buffa, byte1 buffa, byte0 sample 0 sample 0 sample 0 sample 0 +0x4 buffb, byte3 buffb, byte2 buffb, byte1 buffb, byte0 sample 0 sample 0 sample 0 sample 0 +0x8 buffa, byte3 buffa, byte2 buffa, byte1 buffa, byte0 sample 1 sample 1 sample 1 sample 1 +0xc buffb, byte3 buffb, byte2 buffb, byte1 buffb, byte0 sample 1 sample 1 sample 1 sample 1 +0x10 buffa, byte3 buffa, byte2 buffa, byte1 buffa, byte0 sample 2 sample 2 sample 2 sample 2 etc. for a given channel, the minimum input-to-output latency for the chi data path is (4 cycles) (62.5 s) = 250 s, assuming an 8 khz frame rate. these required 4 cycles are as follows: ? 1 cycle to load receive shift register into receive holding register ? 1 cycle for dma of receive holding register data into receive memory space ? (insert here any application-specific time required for processing of received data and moving result to transmit memory space) ? 1 cycle for dma of data in transmit memory space to transmit holding register ? 1 cycle to load transmit holding register data into transmit shift register www.datasheet.in chapter 7 chi module 7-14 half-buffer and end-of-buffer dma address counter interrupts are available, allowing the cpu to minimize overhead and utilize the dma buffer in a ping-pong fashion. for transmit mode, the cpu can use these interrupts to fill or write one half of the buffer while the other half is being emptied by the dma controller for transmitting out the chi. similarly, for receive mode, the cpu can use these interrupts to empty or read one half of the buffer while the other half is being filled by the dma controller from received chi input samples. also available is a direct cpu read/write mode for bypassing the dma, allowing the cpu to read or write the chi data on a sample by sample basis, if so desired. separate dma enables for receive and transmit allow dma to be setup for receive only (transmit via cpu), transmit only (receive via cpu), receive and transmit, or none (receive and transmit via cpu). the dma circuit also provides an interrupt each time the dma buffer pointer is incremented, which occurs whenever a new sample is read from and/or written to the dma buffer. this interrupt may be useful for triggering a read of the dma pointer status value, which is the actual 12-bit dma address counter output. this value indicates exactly where the current address is pointing to in the overall dma buffer. 7.3.6 related interrupts chi0_5int: issues an interrupt whenever the chi dma buffer pointer has reached the halfway point. chi1_0int: issues an interrupt whenever the chi dma buffer pointer has reached the end-of-buffer point. chidmacntint: issues an interrupt each time the chi dma buffer pointer is incremented, which occurs whenever a new chi sample is read from and/or written to the chi dma buffer. chiininta: issues an interrupt whenever a valid chi input sample is available from chi rx holding register a; this also means a valid chi output sample can be written to chi tx holding register a. chiinintb: issues an interrupt whenever a valid chi input sample is available from chi rx holding register b; this also means a valid chi output sample can be written to chi tx holding register b. chiactint: issues an interrupt whenever chiclk is active. this is used for chi wakeup purposes. chierrint: issues an interrupt whenever a chi error is received. this interrupt is triggered if cpu or dma reading of the chi rx holding registers does not keep up with the hardware filling of the chi rx holding registers or if cpu or dma writing of the chi tx holding registers does not keep up with the hardware emptying of the chi tx holding registers. www.datasheet.in chapter 7 chi module 7-15 7.4 chi registers 7.4.1 chi control register offset = $1d8: bit label reset read/write 31-30 reserved 29 chiloop 0 r/w 28 chientest 0 r/w 27 chifsdir 0 r/w 26-25 chifswidth[1:0] x r/w 24-20 chinchan[4:0] x r/w 19-16 chitxboff[3:0] x r/w 15-12 chirxboff[3:0] x r/w 11 txmsbfirst x r/w 10 rxmsbfirst x r/w 9 chirxfspol x r/w 8 chitxfspol x r/w 7chirxedge x r/w 6chitxedge x r/w 5chifsedge x r/w 4 chitxfsedge x r/w 3 chiclk2xmode 0 r/w 2chirxen 0 r/w 1chitxen 0 r/w 0 enchi 0 r/w chiloop: this bit is used for ic testing and should not be set. setting this bit to a logic ?1? will cause the chi serial transmitted data to be internally looped back to the chi serial receive data path. the data is inverted when this mode is selected. clearing this bit to a logic ?0? selects the normal chidin pin as the chi serial receive data source. chientest: this bit is used for ic testing and should not be set. chifsdir: this bit controls the direction of the chifs pin. setting this bit to a logic ?1? configures chifs to be an output (chi sync master mode). clearing this bit to a logic ?0? configures chifs to be an input (chi sync slave mode). note that chirxfspol and chifsedge bits must be set to proper values even when chifsdir is set to a logic ?1? (chi sync master mode). www.datasheet.in chapter 7 chi module 7-16 chifswidth[1:0]: these bits are used to select pulse width for the chifs signal, relevant whenever the chi module is configured as master mode. the pulse width is counted by data bit width. (in clk2x mode, two chiclks correspond to one data bit.) the available chifs pulse widths are as follows: chifswidth chifs pulse width 0 1 bit wide 1 2 bits wide 2 1 byte wide 3 half-frame wide chinchan[4:0]: these bits are used to program the number of 8-bit channel timeslots per half-frame, up to 32 total per half-frame. the value loaded for chinchan is the desired number of channels-1. chitxboff[3:0]: these bits select the transmit data programmable bit offset, which is related to the number of clocks from the start of timeslot 0 (1st timeslot) transmit data to the chifs edge used to trigger the start of each chi frame. the value loaded for chitxboff must be chosen from table 7.2.2 according to the configuration. chirxboff[3:0]: these bits select the receive data programmable bit offset, which is related to the number of clocks from the start of timeslot 0 (1st timeslot) receive data to the chifs edge used to trigger the start of each chi frame. the value loaded for chirxboff must be chosen from table 7.2.1 according to the configuration. txmsbfirst: this bit selects between msb-first and lsb-first serial data formats for each byte of the chi transmit data. setting this bit to a logic ?1? selects msb-first. clearing this bit to a logic ?0? selects lsb-first. rxmsbfirst: this bit selects between msb-first and lsb-first serial data formats for each byte of the chi receive data. setting this bit to a logic ?1? selects msb-first. clearing this bit to a logic ?0? selects lsb-first. chirxfspol: this bit selects between positive (active high) or negative (active low) polarity for the received chifs signal pulse. this bit must be properly set in chi sync master mode, as well as in chi sync slave mode; in chi sync master mode, chirxfspol must be equal to chitxfspol. setting this bit to a logic ?1? selects negative polarity for the chifs pulse. in this case, the falling edge of the chifs pulse is used to trigger the start of the chi frame period. clearing this bit to a logic ?0? selects positive polarity for the chifs pulse. in this case, the rising edge of the chifs pulse is used to trigger the start of the chi frame period. www.datasheet.in chapter 7 chi module 7-17 chitxfspol: this bit selects between positive (active high) or negative (active low) polarity for the transmitted chifs signal pulse, relevant whenever the chi module is configured as master mode. setting this bit to a logic ?1? selects negative polarity for the chifs pulse. clearing this bit to a logic ?0? selects positive polarity for the chifs pulse. chirxedge: this bit selects whether to use either the rising edge or falling edge of chiclk to sample the receive data chidin. setting this bit to a logic ?1? selects rising edge. clearing this bit to a logic ?0? selects falling edge. chidin must be stable before and after the specified chiclk edge. chitxedge: this bit selects whether to use either the rising edge or falling edge of chiclk to clock out the transmit data chidout. setting this bit to a logic ?1? selects rising edge. clearing this bit to a logic ?0? selects falling edge. chifsedge: this bit selects whether to use either the rising edge or falling edge of chiclk to sample the receive frame sync chifs. this bit must be properly set in chi sync master mode, as well as in chi sync slave mode. setting this bit to a logic ?1? selects rising edge. clearing this bit to a logic ?0? selects falling edge. chifs must be stable before and after the specified chiclk edge; in chi sync master mode, chifsedge must be equal to inverted chitxfsedge. chitxfsedge: this bit selects whether to use either the rising edge or falling edge of chiclk to clock out the transmit frame sync chifs, relevant whenever the chi module is configured as master mode. setting this bit to a logic ?1? selects rising edge. clearing this bit to a logic ?0? selects falling edge. chiclk2xmode: this bit selects between 1x and 2x clock modes. setting this bit to a logic ?1? selects 2x clock mode, which means that the chiclk frequency equals twice the serial data bit rate. clearing this bit to a logic ?0? selects 1x clock mode, which means that the chiclk frequency equals the serial data bit rate. chirxen: this bit is used to enable/disable chi receive processing in the direct cpu read/write mode, where the cpu reads the received data through the chi rx holding register. setting this bit to a logic ?1? enables chi receive processing. clearing this bit to a logic ?0? disables chi receive processing, causing all received data to not be processed by the chi module. this bit has no effect when rx dma is enabled. chitxen: this bit is used to enable/disable chi transmit processing in the direct cpu read/write mode, where the cpu writes the data to be transmitted through the chi tx holding register. setting this bit to a logic ?1? enables chi transmit processing. clearing this bit to a logic ?0? disables chi transmit processing, causing the chi serial transmitted data to be tri-stated. this bit has no effect when tx dma is enabled. www.datasheet.in chapter 7 chi module 7-18 enchi: this bit is used to enable/disable the chi module. setting this bit to a logic ?1? enables the chi module. clearing this bit to a logic ?0? disables the chi module and keeps the module in a reset state but gives no effect on the chi control register. to begin the chi operation, follow the procedure below. 1) set up all the configuration registers except chirxen, chitxen, endmarxchi, endmatxchi, and enchi bits. 2) set either chirxen or endmarxchi, and/or, either chitxen or endmatxchi, to a logic ?1?. 3) set enchi to a logic ?1?. to finish the chi operation. 1) clear enchi to a logic ?0?. 2) clear endmarxchi and/or endmatxchi to a logic ?0?, if they were previously set. 7.4.2 chi pointer enable register offset = $1dc: bit label reset read/write 31 chitxptrb3en x r/w 30 chitxptrb2en x r/w 29 chitxptrb1en x r/w 28 chitxptrb0en x r/w 27 chitxptra3en x r/w 26 chitxptra2en x r/w 25 chitxptra1en x r/w 24 chitxptra0en x r/w 23 chirxptrb3en x r/w 22 chirxptrb2en x r/w 21 chirxptrb1en x r/w 20 chirxptrb0en x r/w 19 chirxptra3en x r/w 18 chirxptra2en x r/w 17 chirxptra1en x r/w 16 chirxptra0en x r/w 15-0 reserved x r/w chitxptrb3en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptrb3. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptrb2en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptrb2. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptrb1en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptrb1. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. www.datasheet.in chapter 7 chi module 7-19 chitxptrb0en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptrb0. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptra3en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptra3. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptra2en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptra2. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptra1en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptra1. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chitxptra0en: this bit is used to enable/disable the timeslot for the transmit channel pointed to by the tdm switch pointer chitxptra0. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptrb3en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptrb3. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptrb2en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptrb2. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptrb1en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptrb1. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptrb0en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptrb0. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptra3en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptra3. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. www.datasheet.in chapter 7 chi module 7-20 chirxptra2en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptra2. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptra1en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptra1. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. chirxptra0en: this bit is used to enable/disable the timeslot for the receive channel pointed to by the tdm switch pointer chirxptra0. setting this bit to a logic ?1? enables the timeslot. clearing this bit to a logic ?0? disables the timeslot. 7.4.3 chi receive pointer a register offset = $1e0: write-only bit label reset read/write 31-29 reserved 28-24 chirxptra3[4:0] x w 23-21 reserved 20-16 chirxptra2[4:0] x w 15-13 reserved 12-8 chirxptra1[4:0] x w 7-5 reserved 4-0 chirxptra0[4:0] x w chirxptra3[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 3 of the chi receive holding register a; register a handles all timeslots from channel 0 to channel chinchan . chirxptra2[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 2 of the chi receive holding register a; register a handles all timeslots from channel 0 to channel chinchan. chirxptra1[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 1 of the chi receive holding register a; register a handles all timeslots from channel 0 to channel chinchan. chirxptra0[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 0 of the chi receive holding register a; register a handles all timeslots from channel 0 to channel chinchan. www.datasheet.in chapter 7 chi module 7-21 7.4.4 chi receive pointer b register offset = $1e4: write-only bit label reset read/write 31-29 reserved 28-24 chirxptrb3[4:0] x w 23-21 reserved 20-16 chirxptrb2[4:0] x w 15-13 reserved 12-8 chirxptrb1[4:0] x w 7-5 reserved 4-0 chirxptrb0[4:0] x w chirxptrb3[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 3 of the chi receive holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2 + 1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chirxptrb2[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 2 of the chi receive holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2 + 1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chirxptrb1[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 1 of the chi receive holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2 + 1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chirxptrb0[4:0]: write-only these bits represent the tdm switch pointer which defines the receive channel timeslot for byte 0 of the chi receive holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2 + 1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). www.datasheet.in chapter 7 chi module 7-22 7.4.5 chi transmit pointer a register offset = $1e8: write-only bit label reset read/write 31-29 reserved 28-24 chitxptra3[4:0] x w 23-21 reserved 20-16 chitxptra2[4:0] x w 15-13 reserved 12-8 chitxptra1[4:0] x w 7-5 reserved 4-0 chitxptra0[4:0] x w chitxptra3[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 3 of the chi transmit holding register a; register a handles all timeslots from channel 0 to channel chinchan. chitxptra2[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 2 of the chi transmit holding register a; register a handles all timeslots from channel 0 to channel chinchan. chitxptra1[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 1 of the chi transmit holding register a; register a handles all timeslots from channel 0 to channel chinchan. chitxptra0[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 0 of the chi transmit holding register a; register a handles all timeslots from channel 0 to channel chinchan. www.datasheet.in chapter 7 chi module 7-23 7.4.6 chi transmit pointer b register offset = $1ec: write-only bit label reset read/write 31-29 reserved 28-24 chitxptrb3[4:0] x w 23-21 reserved 20-16 chitxptrb2[4:0] x w 15-13 reserved 12-8 chitxptrb1[4:0] x w 7-5 reserved 4-0 chitxptrb0[4:0] x w chitxptrb3[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 3 of the chi transmit holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2?1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chitxptrb2[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 2 of the chi transmit holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2?1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chitxptrb1[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 1 of the chi transmit holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2?1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). chitxptrb0[4:0]: write-only these bits represent the tdm switch pointer which defines the transmit channel timeslot for byte 0 of the chi transmit holding register b; register b handles all timeslots from channel (chinchan + 1) to channel (chinchan 2?1) . the value loaded for this tdm switch pointer is the desired timeslot number minus (chinchan + 1). www.datasheet.in chapter 7 chi module 7-24 7.4.7 chi size register offset = $1f0: bit label reset read/write 31-30 reserved 29-18 chidmaptr[13:2] ? r 17-16 reserved 15 chibuff1time 0 r/w 14 chidmaloop 0 r/w 13-2 chisize[13:2] x w 1 endmarxchi 0 r/w 0 endmatxchi 0 r/w chidmaptr[13:2]: read-only these bits provide the status of the chi dma counter. chibuff1time: the chi dma controller supports two buffer addressing modes depending on the state of this bit. when chibuff1time is set to a logic ?1?, the chi dma controller will stop executing when it reaches the end of the dma buffer. when chibuff1time is cleared to a logic ?0?, the chi dma controller will loop back to the start of the dma buffer when the end of the dma buffer is reached and will continue operating in a continuous and circular manner. chidmaloop: the chi dma controller supports two full-duplex loopback modes depending on the state of this bit. when chidmaloop is set to a logic ?1?, the chi dma controller issues rx dma requests first, followed by tx dma requests. this ordering allows an rx-to-tx immediate loopback via the dma buffer. when chidmaloop is cleared to a logic ?0?, the chi dma controller issues tx dma requests first, followed by rx dma requests. this ordering allows a single circular dma buffer to be used for both tx and rx, if so desired. chisize (13:2): write-only these bits define the size of the chi dma buffers (16 kbytes maximum). both the chi rx buffer and the chi tx buffer are the same size. the last address in the chi rx dma buffer is given by chirxstart[31:2] + chisize[13:2]. the last address in the chi tx dma buffer is given by chitxstart[31:2] + chisize[13:2]. the value loaded into chisize should be equal to the desired buffer length ? 1. endmarxchi: this bit enables the chi dma receive function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the chirxstart, chitxstart, and chisize registers are setup. to enable chi dma receive function, this bit must be set before the chi module is enabled (enchi asserted). either endmarxchi or endmatxchi or both can be set at a time since the chi dma controller can support full duplex operation. www.datasheet.in chapter 7 chi module 7-25 endmatxchi: this bit enables the chi dma transmit function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the chirxstart, chitxstart, and chisize registers are setup. to enable chi dma transmit function, this bit must be set before the chi module is enabled (enchi asserted). either endmarxchi or endmatxchi or both can be set at a time since the chi dma controller can support full duplex operation. 7.4.8 chi rx start register offset = $1f4: write-only bit label reset read/write 31-2 chirxstart[31:2] x w 1-0 reserved chirxstart[31:2]: write-only these bits define the start address for the chi rx dma buffer. the chi rx buffer and chi tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). 7.4.9 chi tx start register offset = $1f8: write-only bit label reset read/write 31-2 chitxstart[31:2] x w 1-0 reserved chitxstart[31:2]: write-only these bits define the start address for the chi tx dma buffer. the chi rx buffer and chi tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). www.datasheet.in chapter 7 chi module 7-26 7.4.10 chi tx holding register offset = $1fc: write-only bit label reset read/write 31-0 chitxhold[31:0] x w chitxhold[31:0]: write-only these bits represent the chi data to be transmitted. chi data can be either written directly to this register by the cpu or transparently read from the chi tx dma buffer to this register. this register should only be loaded by the cpu after the chiininta or chiinintb interrupt is asserted. the write immediately after chiininta updates the internal tx holding register a and the write immediately after chiinintb updates the internal tx holding register b. transmit data for bytes 3, 2, 1, and 0 are loaded into the 32-bit chitxhold at locations [31:24], [23:16], [15:8], and [7:0], respectively. these data bytes correspond to the chi timeslots as defined by the values in the chitxptra and chitxptrb tdm switch registers. 7.4.11 chi rx holding register offset = $1fc: read-only bit label reset read/write 31-0 chirxhold[31:0] x r chirxhold[31:0]: read-only these bits represent the chi data to be received. chi data can be either read directly from this register by the cpu or transparently written to the chi rx dma buffer from this register. this register should only be read by the cpu after the chiininta or chiinintb interrupt is asserted. the read immediately after chiininta sees the internal rx holding register a and the read immediately after chiinintb sees the internal rx holding register b. receive data for bytes 3, 2, 1, and 0 are stored into the 32-bit chirxhold at locations [31:24], [23:16], [15:8], and [7:0], respectively. these data bytes correspond to the chi timeslots as defined by the values in the chirxptra and chirxptrb tdm switch registers. www.datasheet.in chapter 8 interrupt module 8-1 8. interrupt module 8.1 overview the interrupt module within the TMPR3911/12 contains logic for reading, enabling, and clearing all of the interrupt sources. these interrupts are either generated from internal TMPR3911/12 modules or from edge transitions on external signal pins. all of these latter interrupt types generate a separate positive and negative edge interrupt. the status (logic state) of each interrupt is readable, allowing any interrupt event to be polled, if desired. each interrupt status signal is also gated with the corresponding interrupt enable bit in order to generate the overall irq output to the cpu. the interrupt status register is reset using the corresponding clear bit from the corresponding clear interrupt register. www.datasheet.in chapter 8 interrupt module 8-2 8.2 implementation 8.2.1 block diagram irq block diagram 16 located within individual module individual int status individual set int pri encoder enable int reg out note: ?x? corresponds to appropriate interrupt register number individual int enable wrclrintx wrintxen data bus in rdintxen in 4 1 16 1 15 global int enable int status reg individual clr int or tree data bus out int vector irq irqhigh ir q low priority mask rdintx reset rst set out priority int?s int2 of tx39/h core int4 of tx39/h core cpcond3 of tx39/h core figure 8.2.1 interrupt circuit block diagram www.datasheet.in chapter 8 interrupt module 8-3 8.2.2 interrupt logic description figure 8.2.1 shows a block diagram of the interrupt circuit for a single interrupt source. every other interrupt source contains an identical circuit. the overall interrupt module contains 5 main sets of registers (numbered 1 through 5), with a 6th register allocated for setting the global interrupt enable and the 16-bit priority mask, and for reading the priority interrupt vector and irqhigh and irqlow status bits. each bit within each of the 5 main sets then consists of 3 registers: status, enable, and clear. ? interrupt status register read-only ? allows cpu to read logic state of interrupt status ? informs the cpu which interrupts are pending ? enable interrupt register read/write ? allows cpu to enable a given interrupt ? each individual interrupt has a corresponding enable bit ? clear interrupt register write-only ? allows cpu to clear a given pending interrupt ? each individual interrupt has a corresponding clear bit ? each individual interrupt clear address and bit position maps one-to-one with the interrupt status address and bit position (status transactions are cpu reads, clear transactions are cpu writes) a given interrupt status register is set by the corresponding individual interrupt event. for example, this event could be a positive (or negative) edge transition on an external TMPR3911/12 pin. another example might be an event triggered by an internal TMPR3911/12 module, such as a particular dma buffer reaching the end-of-buffer point. the output of a given interrupt status register is readable by the cpu, by reading the address which points to the corresponding interrupt status register. a given interrupt is enabled by writing a ?1? to the corresponding bit position in the corresponding enable interrupt register. the interrupt status register output bit is then gated with the enable bit from the corresponding enable interrupt register. the output of this gate is then combined with all the other gated interrupt status bits using a wide bitwise ?or? tree in order to generate the irqlow status signal. in other words, if any of the gated interrupt status signals is asserted and the global interrupt enable globalen is asserted, then irqlow will be asserted. www.datasheet.in chapter 8 interrupt module 8-4 a given pending interrupt is cleared by writing a ?1? to the corresponding bit position in the corresponding clear interrupt register. the output of this clear interrupt register is used to reset the corresponding interrupt status register. on power on reset, the global enable is cleared to prevent any interrupts from occurring until the enable interrupt registers are initialized. also, all clear interrupts will be set for the duration of reset (thus interrupts cleared). the interrupt module also contains 15 high priority interrupt sources. a 16-bit priority mask (located within the enable interrupt 6 register) is used to enable any of these high priority interrupts, by writing a ?1? to the corresponding bit position in the enable interrupt 6 register, where bit 15 is the highest priority. each bit of the 16-bit priority mask is gated with the corresponding 15 high priority interrupt signals and these gated signals are then combined using a bitwise 16-input ?or? tree in order to generate the irqhigh status signal. if irqhigh or irqlow is asserted, then the overall irq will be asserted. a priority encoder circuit also compares the 16-bit priority mask with the 15 high priority interrupt signals and generates a 4-bit interrupt status vector which points to the highest priority pending interrupt from the set of 16 possible events. level 15 is the highest priority and level 1 is the lowest priority, with level 0 corresponding to the standard interrupt handler. the irqhigh signal is connected to interrupt bit 4 on the tx39/h processor core and the irqlow signal is connected to interrupt bit 2. the irqhigh signal is also connected to cpu co-processor condition bit 3. www.datasheet.in chapter 8 interrupt module 8-5 8.3 interrupt registers 8.3.1 interrupt status 1 register offset = $100: read-only bit label reset read/write 31 lcdint ? r 30 dfint ? r 29 chi0_5int ? r 28 chi1_0int ? r 27 chidmacntint ? r 26 chininta ? r 25 chinintb ? r 24 chiactint ? r 23 chierrint ? r 22 snd0_5int ? r 21 snd1_0int ? r 20 tel0_5int ? r 19 tel1_0int ? r 18 snddmacntint ? r 17 teldmacntint ? r 16 lsndclipint ? r 15 rsndclipint ? r 14 valsndposint ? r 13 valsndnegint ? r 12 valtelposint ? r 11 valtelnegint ? r 10 sndinint ? r 9telinint ? r 8sibsf0int ? r 7sibsf1int ? r 6sibirqnegint ? r 5sibirqnegint ? r 4-0 reserved ? r lcdint: issues an interrupt at the end of each video frame. dfint: issues an interrupt each time the video df signal toggles. chi0_5int: issues an interrupt whenever the chi dma buffer pointer has reached the halfway point. chi1_0int: issues an interrupt whenever the chi dma buffer pointer has reached the end-of-buffer point. chidmacntint: issues an interrupt each time the chi dma buffer pointer is incremented, which occurs whenever a new chi sample is read from and/or written to the chi dma buffer. www.datasheet.in chapter 8 interrupt module 8-6 chiininta: issues an interrupt whenever a valid chi input sample is available from chi rx holding register a; this also means a valid chi output sample can be written to chi tx holding register b. chiinintb: issues an interrupt whenever a valid chi input sample is available from chi rx holding register b; this also means a valid chi output sample can be written to chi tx holding register a. chiactint: issues an interrupt whenever chiclk is active. this is used for chi wakeup purposes. chierrint: issues an interrupt whenever a chi error is received. this interrupt is triggered if cpu or dma reading of the chi rx holding registers does not keep up with the hardware filling of the chi rx holding registers or if cpu or dma writing of the chi tx holding registers does not keep up with the hardware emptying of the chi tx holding registers. snd0_5int: issues an interrupt whenever the sound dma buffer pointer has reached the halfway point. snd1_0int: issues an interrupt whenever the sound dma buffer pointer has reached the end-of-buffer point. tel0_5int: issues an interrupt whenever the telecom dma buffer pointer has reached the halfway point. tel1_0int: issues an interrupt whenever the telecom dma buffer pointer has reached the end-of-buffer point. snddmacntint: issues an interrupt each time the sound dma buffer pointer is incremented, which occurs whenever a new sound sample is read from and/or written to the sound dma buffer. teldmacntint: issues an interrupt each time the telecom dma buffer pointer is incremented, which occurs whenever a new telecom sample is read from and/or written to the telecom dma buffer. lsndclipint: issues an interrupt whenever the amplitude of the left channel sound data is clipping the codec a/d converter for sib subframe 1. rsndclipint: issues an interrupt whenever the amplitude of the right channel sound data is clipping the codec a/d converter for sib subframe 1. www.datasheet.in chapter 8 interrupt module 8-7 valsndposint: issues an interrupt whenever the valid sound status flag transitions from a logic ?0? to a logic ?1?. this valid flag is triggered from sib subframe 0 (if selsndsf1 = ?0?) or from sib subframe 1 (if selsndsf1 = ?1?). valsndnegint: issues an interrupt whenever the valid sound status flag transitions from a logic ?1? to a logic ?0?. this valid flag is triggered from sib subframe 0 (if selsndsf1 = ?0?) or from sib subframe 1 (if selsndsf1 = ?1?). va lt e l p o s i n t: issues an interrupt whenever the valid telecom status flag transitions from a logic ?0? to a logic ?1?. this valid flag is triggered from sib subframe 0 (if seltelsf1 = ?0?) or from sib subframe 1 (if seltelsf1 = ?1?). valtelnegint: issues an interrupt whenever the valid telecom status flag transitions from a logic ?1? to a logic ?0?. this valid flag is triggered from sib subframe 0 (if seltelsf1 = ?0?) or from sib subframe 1 (if seltelsf1 = ?1?). sndinint: issues an interrupt whenever a valid sound input longword (32 bits) is available from the sound rx holding register; this also means a valid sound output longword can be written to the sound tx holding register. telinint: issues an interrupt whenever a valid telecom input longword (32 bits) is available from the telecom rx holding register; this also means a valid telecom output longword can be written to the telecom tx holding register. sibsf0int: issues an interrupt at the start of every sib subframe 0. this is used to initiate cpu reading of the sib subframe 1 status register (sf1stat register) and/or cpu writing of the sib subframe 0 control register (sf0aux register). sibsf1int: issues an interrupt at the start of every sib subframe 1. this is used to initiate cpu reading of the sib subframe 0 status register (sf0stat register) and/or cpu writing of the sib subframe 1 control register (sf1aux register). sibirqposint: issues an interrupt whenever the sibirq pin transitions from a logic ?0? to a logic ?1?. sibirqnegint: issues an interrupt whenever the sibirq pin transitions from a logic ?1? to a logic ?0?. www.datasheet.in chapter 8 interrupt module 8-8 8.3.2 interrupt status 2 register offset = $104: read-only bit label reset read/write 31 uartarxint ? r 30 uartarxoverrunint ? r 29 uartaframeerrint ? r 28 uartabreakint ? r 27 uartaparityerrint ? r 26 uartatxint ? r 25 uartatxoverrunint ? r 24 uartaemptyint ? r 23 uartadmafullint ? r 22 uartadmahalfint ? r 21 uartbrxint ? r 20 uartbrxoverrunint ? r 19 uartbframeerrint ? r 18 uartbbreakint ? r 17 uartbparityerrint ? r 16 uartbtxint ? r 15 uartbtxoverrunint ? r 14 uartbemptyint ? r 13 uartbdmafullint ? r 12 uartbdmahalfint ? r 11 mbustxbufavallint ? r 10 mbustxerrint ? r 9 mbusemptyint ? r 8 mbusrxbufavallint ? r 7mbusrxerrint ? r 6 mbusdetint ? r 5 mbusdmafullint ? r 4mbusdmahalfint ? r 3 mbusposint ? r 2 mbusnegint ? r 1-0 reserved ? r uartarxint: issues an interrupt if the uarta receive holding register is loaded with data. uartarxoverrunint: issues an interrupt if the uarta receive holding register is loaded twice before the interrupt is service. uartaframeerrint: issues an interrupt if the current data in the uarta receive holding register contains a frame error. uartabreakint: issues an interrupt if the current data in the uarta receive holding register is a break. www.datasheet.in chapter 8 interrupt module 8-9 uartaparityerrint: issues an interrupt if the current data in the uarta receive holding register contains a parity error. uartatxint: issues an interrupt if the uarta transmit holding register is available. uartatxoverrunint: issues an interrupt if the uarta transmit holding register is written to when the transmit holding register is not available. uartaemptyint: issues an interrupt if the uarta transmit holding register and transmit shift register are both empty. uartadmafullint: issues an interrupt if the uarta dma counter reaches the end of the buffer. uartadmahalfint: issues an interrupt if the uarta dma counter reaches the mid point of the buffer. uartbrxint: issues an interrupt if the uartb receive holding register is loaded with data. uartbrxoverrunint: issues an interrupt if the uartb receive holding register is loaded twice before the interrupt is service. uartbframeerrint: issues an interrupt if the current data in the uartb receive holding register contains a frame error. uartbbreakint: issues an interrupt if the current data in the uartb receive holding register is a break. uartbparityerrint: issues an interrupt if the current data in the uartb receive holding register contains a parity error. uartbtxint: issues an interrupt if the uartb transmit holding register is available. uartbtxoverrunint: issues an interrupt if the uartb transmit holding register is written to when the transmit holding register is not available. www.datasheet.in chapter 8 interrupt module 8-10 uartbemptyint: issues an interrupt if the uartb transmit holding register and transmit shift register are both empty. uartbdmafullint: issues an interrupt if the uartb dma counter reaches the end of the buffer. uartbdmahalfint: issues an interrupt if the uartb dma counter reaches the mid point of the buffer. mbustxbufavailint: this interrupt is set when the enmbus bit is first asserted and subsequently when the contents of the mbus transmitter holding register are transferred to the mbus shift register. this interrupt is used to indicate that the mbus transmitter holding register is available to be written by the software. mbustxerrint: issues an interrupt if the magicbus transmit holding register is written to when the transmit holding register is not available. mbusemptyint: issues an interrupt if the magicbus transmit holding register and transmit shift register are both empty. mbusrxbufavailint: issues an interrupt if the magicbus receive holding register is loaded with data. mbusrxerrint: issues an interrupt if the magicbus receive holding register is loaded twice before the interrupt is serviced. mbusdetint: issues an interrupt if the magicbus command word detector triggers. mbusdmafullint: issues an interrupt if the magicbus dma counter reaches the end of the buffer. mbusdmahalfint: issues an interrupt if the magicbus dma counter reaches the mid point of the buffer. mbusposint: issues an interrupt if the mbusint signal goes from a logic ?0? to a logic ?1?. mbusnegint: issues an interrupt if the mbusint signal goes from a logic ?1? to a logic ?0?. www.datasheet.in chapter 8 interrupt module 8-11 8.3.3 interrupt status 3 register offset = $108: read-only bit label reset read/write 31-0 mfioposint[31:0] ? r mfioposint[31:0]: issues an interrupt whenever any of the multi-function i/o pin(s) transition from a logic ?0? to a logic ?1?. there are a total of 32 multi-function i/o pins (31 thru 0), each of which corresponds to the respective bit within this status register. each multi-function i/o pin can independently trigger an interrupt. 8.3.4 interrupt status 4 register offset = $10c: read-only bit label reset read/write 31-0 mfionegint[31:0] ? r mfionegint[31:0]: issues an interrupt whenever any of the multi-function i/o pin(s) transition from a logic ?1? to a logic ?0?. there are a total of 32 multi-function i/o pins (31 thru 0), each of which corresponds to the respective bit within this status register. each multi-function i/o pin can independently trigger an interrupt. www.datasheet.in chapter 8 interrupt module 8-12 8.3.5 interrupt status 5 register offset = $110: read-only bit label reset read/write 31 rtcint ? r 30 alarmint ? r 29 perint ? r 28 stptimerint ? r 27 pospwrint ? r 26 negpwrint ? r 25 pospwrokint ? r 24 negpwrokint ? r 23 posonbutnint ? r 22 negonbutnint ? r 21 spibufavailint ? r 20 spierrint ? r 19 spircvint ? r 18 spiemptyint ? r 17 irconsmint ? r 16 carstint ? r 15 poscarint ? r 14 negcarint ? r 13-7 ioposint[6:0] ? r 6-0 ionegint[6:0] ? r rtcint: this interrupt is set whenever all 40 bits of the rtc counter reaches a value of ?$ffffffffff? to alert the software that the counter is ?rolling over?. alarmint: this interrupt is set whenever the rtc counter reaches a count that is equal to the value of the alarm[39:0] bits set in the alarm register. perint: this interrupt is set whenever the periodic timer is enabled and the periodic timer counter reaches a count of zero. stptimerint: this interrupt is set whenever the stop timer counter counts up to the value set by the stptimerval[3:0] control bits. www.datasheet.in chapter 8 interrupt module 8-13 stptimerint: this interrupt is set whenever the stop timer counter counts up to the value set by the stptimerval[3:0] control bits. pospwrint: this interrupt is set whenever the pwrint pin transitions from a logic ?0? to a logic ?1?. negpwrint: this interrupt is set whenever the pwrint pin transitions from a logic ?1? to a logic ?0?. pospwrokint: issues an interrupt whenever the pwrok signal transitions from a logic ?0? to a logic ?1?. negpwrokint: issues an interrupt whenever the pwrok signal transitions from a logic ?1? to a logic ?0?. posonbutnint: issues an interrupt whenever the onbutn signal transitions from a logic ?0? to a logic ?1?. if the dbnconbutn control bit is set, then the interrupt will not set until the signal is debounced for 16-24 ms. negonbutnint: issues an interrupt whenever the onbutn signal transitions from a logic ?1? to a logic ?0?. if the dbnconbutn control bit is set, then the interrupt will not set until the signal is debounced for 16-24 ms. spibufavailint: this interrupt is set whenever the enspi bit is first asserted and subsequently when the contents of the spi transmitter holding register are transferred to the spi shift register. this interrupt is used to indicate that the spi transmitter holding register is available to be written by the software. spierrint: this interrupt is set whenever the spi transmitter holding register is written, but the spibufavailint has not set to indicate that the register is available. this interrupt serves as an overrun indication for the software. www.datasheet.in chapter 8 interrupt module 8-14 spircvint: this interrupt is set whenever the contents of the spi shift register are transferred to the spi receiver holding register. this interrupt is used to indicate that there is valid data in the spi receiver holding register to be read by the software. spiemptyint: this interrupt is set whenever the both the spi shift register and the spi transmitter holding register are empty. this interrupt can be used by the software to determine when the spi is idle. irconsmint: whenever the upper byte of data is loaded into the 7-bit period number counter, the lower byte of data is loaded into an intermediate holding register. at this time the 16-bit ir holding register is empty. the irconsmint interrupt is then set to inform the cpu that the ir holding register is available. the cpu must fill the next word of data into the ir holding register before the 7-bit period number counter is finished counting the periods for both the upper and lower bytes of data. carstint: this interrupt is set whenever the carrier detect state machine detects the cardet pin is high just before turning off the rxpwr pin. poscarint: this interrupt is set whenever cardet pin transitions from a logic ?0? to a logic ?1?. negcarint: this interrupt is set whenever cardet pin transitions from a logic ?1? to a logic ?0?. ioposint (6:0): issues an interrupt whenever any of the general purpose i/o pin(s) transitions from a logic ?0? to a logic ?1?. there are a total of 7 general purpose i/o pins (6 thru 0), each of which corresponds to the respective bit within this status register. each general purpose i/o pin can independently trigger an interrupt. ionegint (6:0): issues an interrupt whenever any of the general purpose i/o pin(s) transitions from a logic ?1? to a logic ?0?. there are a total of 7 general purpose i/o pins (6 thru 0), each of which corresponds to the respective bit within this status register. each general purpose i/o pin can independently trigger an interrupt. www.datasheet.in chapter 8 interrupt module 8-15 8.3.6 interrupt status 6 register offset = $114: read-only bit label reset read/write 31 irqhigh ? r 30 irqlow ? r 29 pwroknmi 0 r/w 28-6 reserved 5-2 intvect[3:0] ? r 1-0 reserved irqhigh: this status bit is the bitwise ?or? of all the 16 possible high priority interrupts. irqlow: this status bit is the bitwise ?or? of all the interrupts contained in the interrupt status 1, 2, 3, 4, and 5 registers. pwroknmi: when this bit is set, input to the pwrok pin can be used as the nmi source for the tx39/h core. when the bit is cleared, nmi for the tx39/h core is disabled. intvect[3:0]: these 4 status bits indicate a vector pointing to the highest priority pending interrupt from the set of 16 possible high priority interrupt events. the set of high priority interrupts is listed below, where level 15 is the highest priority and level 1 is the lowest priority. level 0 corresponds to the standard interrupt handler. priority level high priority interrupt source 15 pospwrokint or negpwrokint 14 alarmint 13 perint 12 mbusposint or mbusnegint 11 uartarxint 10 uartbrxint 9 mfioposint (19) or mfioposint (18) or mfioposint (17) or mfioposint (16) 8 mfioposint (1) or mfioposint (0) or ioposint (6) or ioposint (5) 7 mfionegint (19) or mfionegint (18) or mfionegint (17) or mfionegint (16) 6 mfionegint (1) or mfionegint (0) or ionegint (6) or ionegint (5) 5 mbusdmafullint 4 snddmacntint 3teldmacntint 2 chidmacntint 1 ioposint (0) or ionegint (0) www.datasheet.in chapter 8 interrupt module 8-16 8.3.7 clear interrupt 1 register offset = $100: write-only the clear interrupt 1 register bit locations are mapped on a one to one basis with the interrupt status 1 register. a logic ?1? written to a specific bit location will clear the corresponding bit in the status register. 8.3.8 clear interrupt 2 register offset = $104: write-only the clear interrupt 2 register bit locations are mapped on a one to one basis with the interrupt status 2 register. a logic ?1? written to a specific bit location will clear the corresponding bit in the status register. 8.3.9 clear interrupt 3 register offset = $108: write-only the clear interrupt 3 register bit locations are mapped on a one to one basis with the interrupt status 3 register. a logic ?1? written to a specific bit location will clear the corresponding bit in the status register. 8.3.10 clear interrupt 4 register offset = $10c: write-only the clear interrupt 4 register bit locations are mapped on a one to one basis with the interrupt status 4 register. a logic ?1? written to a specific bit location will clear the corresponding bit in the status register. 8.3.11 clear interrupt 5 register offset = $110: write-only the clear interrupt 5 register bit locations are mapped on a one to one basis with the interrupt status 5 register. a logic ?1? written to a specific bit location will clear the corresponding bit in the status register. 8.3.12 enable interrupt 1 register offset = $118: read/write the enable interrupt 1 register bit locations are mapped on a one to one basis with the interrupt status 1 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. this register is not cleared upon reset; however, the globalen global interrupt enable bit is cleared upon reset, therefore disabling all interrupts. www.datasheet.in chapter 8 interrupt module 8-17 8.3.13 enable interrupt 2 register offset = $11c: read/write the enable interrupt 2 register bit locations are mapped on a one to one basis with the interrupt status 2 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. this register is not cleared upon reset; however, the globalen global interrupt enable bit is cleared upon reset, therefore disabling all interrupts. 8.3.14 enable interrupt 3 register offset = $120: read/write the enable interrupt 3 register bit locations are mapped on a one to one basis with the interrupt status 3 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. this register is not cleared upon reset; however, the globalen global interrupt enable bit is cleared upon reset, therefore disabling all interrupts. 8.3.15 enable interrupt 4 register offset = $124: read/write the enable interrupt 4 register bit locations are mapped on a one to one basis with the interrupt status 4 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. this register is not cleared upon reset; however, the globalen global interrupt enable bit is cleared upon reset, therefore disabling all interrupts. 8.3.16 enable interrupt 5 register offset = $128: read/write the enable interrupt 5 register bit locations are mapped on a one to one basis with the interrupt status 5 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. this register is not cleared upon reset; however, the globalen global interrupt enable bit is cleared upon reset, therefore disabling all interrupts. www.datasheet.in chapter 8 interrupt module 8-18 8.3.17 enable interrupt 6 register offset = $12c: read/write the enable interrupt 6 register bit locations are mapped on a one to one basis with the interrupt status 6 register. a logic ?1? written to a specific bit location will enable the corresponding interrupt in the status register. bit label reset read/write 31-19 reserved 18 globalen 0 r/w 17 irqpritest 0 r/w 16 irqtest 0 r/w 15-0 prioritymask[15:0] x r/w globalen: this is used as a global interrupt enable for all interrupts, and is cleared upon reset, therefore disabling all interrupts. irqpritest: this bit is used for ic testing and should not be set. irqtest: this bit is used for ic testing and should not be set. prioritymask[15:0]: these bits are an enable mask for the 16 possible high priority interrupts, where bit 15 is the highest priority. a logic ?1? written to a specific bit location will enable the corresponding high priority interrupt. www.datasheet.in chapter 9 i/o module 9-1 9. i/o module 9.1 overview the i/o module within the TMPR3911/12 contains support for reading and writing the 7 bi-directional general purpose i/o pins and the 32 bi-directional multi-function i/o pins. each of the general purpose i/o pins can be independently configured as an input or output port. each port can generate a separate positive and negative edge interrupt and each port can also be independently configured to use a debouncer. of the 137 signal pins found on the TMPR3911/12, 32 of them are multi-function and can be independently programmed either as i/o ports or for an alternate standard/normal function. this allows the TMPR3911/12 to support a flexible and wide range of system applications and configurations. as an i/o port, any of these pins can be programmed as an input or output port, with the capability of generating a separate positive and negative edge interrupt. 9.1.1 related pins i/o[6:0]: input/output these pins are general purpose input/output ports. each port can be independently programmed as an input or output port. each port can generate a separate positive and negative edge interrupt. each port can also be independently programmed to use a 16 ms to 24 ms debouncer. mfio[1:0]: input/output these pins are multi-function input/output ports. each port can be independently programmed as an input or output port, or can be programmed for multi-function use to support test signals (for debugging purposes only). each port can generate a separate positive and negative edge interrupt. note that 30 other multi-function pins are available for usage as multi-function input/output ports. these pins are named according to their respective standard/normal function and are not listed here. www.datasheet.in chapter 9 i/o module 9-2 9.2 implementation 9.2.1 block diagram i/o debounce reg interrupt flip-flop to interrupt module i/o data in reg powerdown i/o direc reg control from cpu i/o pin in out en 8 ms clock 2:1 mux i/o data out reg debounce i/o pwr down reg pwr down figure 9.2.1 general purpose i/o port block diagram www.datasheet.in chapter 9 i/o module 9-3 mfio pin pwr down interrupt flip-flop to interrupt module mfio select reg std func direc mfio data in reg std function data in out std function data out powerdown control from cpu en in mfio pwr down reg mfio direc reg mfio data out reg 2:1 mux 2:1 mux * figure 9.2.2 multi-function i/o port block diagram * chifs, chiclk, chidout, bc32k, txd, spiclk, spiout, sibmclk: each of above signals is directly connected with mux without powerdown combination logic. www.datasheet.in chapter 9 i/o module 9-4 9.2.2 general purpose i/o ports each of the 7 general purpose i/o ports can be independently programmed as an input or output port. each port can generate a separate positive and negative edge interrupt. figure 9.2.1 shows a block diagram of a general purpose i/o port. each port consists of a bi-directional buffer connected to the appropriate TMPR3911/12 pin. for the input direction, the output signal from the input buffer is routed directly to a debounce circuit. this circuit performs a 16 ms to 24 ms debounce of the input signal. the debounce select control signal from the i/o debounce select register is used to select between the debouncer output and the direct signal from the port input buffer, which bypasses the debouncer. this selected signal is then routed to the i/o data input register and to the interrupt flip-flop. reading a specific bit location within the i/o data input register returns the logic state of the respective general purpose i/o pin (either direct or debounced), regardless of whether that pin is configured as an output or input. if the pin is configured as an input, the value read is the logic state of the pin as driven by an external source. if the pin is configured as an output, the value read is the logic state of the pin as driven by the TMPR3911/12. for the output direction, the input signal to the output buffer is routed from the appropriate bit within the i/o data output register. the output enable control signal for the tri-state output buffer is routed from the i/o direction register. the i/o power-down register provides independent control bits for controlling the power-down state for each of the 7 general purpose i/o ports. if a particular i/o port is configured to power down, then the output will be gated low and a pull-down resistor will be enabled whenever the device powers down. device power down occurs when either vcc3 or vccon (internal signal) become de-asserted. the pull-down will prevent the input from floating if the general purpose i/o port is configured as an input. www.datasheet.in chapter 9 i/o module 9-5 9.2.3 multi-function i/o ports each of the 32 multi-function i/o ports can be independently programmed as an input or output port or can be programmed for an alternate standard/normal function. this allows the TMPR3911/12 to support a flexible and wide range of system applications and configurations. as an i/o port, any of these pins can generate a separate positive and negative edge interrupt. figure 9.2.2 shows a block diagram of a multi-function i/o port. each port consists of a bi-directional buffer connected to the appropriate TMPR3911/12 pin. for the input direction, the output signal from the input buffer is routed directly to the mfi/o data input register, to the interrupt flip-flop, and to the appropriate module corresponding to the standard/normal function of the particular port, if this standard use is as an input signal. reading a specific bit location within the mfio data input register returns the logic state of the respective multi-function i/o pin, regardless of whether that pin is configured as an output or input. if the pin is configured as an input, the value read is the logic state of the pin as driven by an external source. if the pin is configured as an output, the value read is the logic state of the pin as driven by the TMPR3911/12. for the output direction, the input signal to the output buffer is routed from a multiplexer which selects between the appropriate bit within the mfio data output register and the signal driven by the appropriate module corresponding to the standard/normal function of the particular port, if this standard use is as an output signal. the output enable control signal for the tri-state output buffer is also routed from a multiplexer which selects between the appropriate bit within the mfio direction register and the direction signal driven by the appropriate module corresponding to the standard use of the particular port, if this standard use is as an output signal. the mfio power-down register provides independent control bits for controlling the power-down state for each of the 32 multi-function i/o ports. if a particular multi-function i/o port is configured to power down, then the output will be gated low and a pull-down resistor will be enabled whenever the device powers down. device power down occurs when either vcc3 or vccon (internal signal) become de-asserted. the pull-down will prevent the input from floating if the multi-function i/o port is configured as an input. www.datasheet.in chapter 9 i/o module 9-6 as mentioned previously, each of the multi-function i/o ports can be independently programmed for routing of signals for a standard/normal function to or from any given multi-function i/o port. table 9.2.1 lists each of these standard functions for each multi-function i/o port. note that depending on the reset state for the respective mfio select register bits, the pin function is configured either as a multi- function port or as a standard function port. table 9.2.1 multi-function i/o ports versus standard functions TMPR3911/12 pin standard function (i = input, o = output) multi-function i/o port multi-function select (reset state) chifs chifs (i/o) mio[31] miosel[31] (1) chiclk chiclk (i/o) mio[30] miosel[30] (1) chidout chidout (o) mio[29] miosel[29] (1) chidin chidin (i) mio[28] miosel[28] (1) dreq * dreq * (i) mio[27] miosel[27] (0) dgrnt * dgrnt * (o) mio[26] miosel[26] (0) bc32k bc32k (o) mio[25] miosel[25] (1) txd txd (o) mio[24] miosel[24] (0) rxd rxd (i) mio[23] miosel[23] (0) cs1 * cs1 * (o) mio[22] miosel[22] (0) cs2 * cs2 * (o) mio[21] miosel[21] (0) cs3 * cs3 * (o) mio[20] miosel[20] (0) mcs0 * mcs0 * (o) mio[19] miosel[19] (1) mcs1 * mcs1 * (o) mio[18] miosel[18] (1) mcs2 * mcs2 * (o) mio[17] miosel[17] (1) mcs3 * mcs3 * (o) mio[16] miosel[16] (1) spiclk spiclk (o) mio[15] miosel[15] (0) spiout spiout (o) mio[14] miosel[14] (0) spiin spiin (i) mio[13] miosel[13] (0) sibmclk sibmclk (i/o) mio[12] miosel[12] (0) cardreg * cardreg * (o) mio[11] miosel[11] (1) cardiowr * cardiowr * (o) mio[10] miosel[10] (1) cardiord * cardiord * (o) mio[9] miosel[9] (1) card1csl * card1csl * (o) mio[8] miosel[8] (1) card1csh * card1csh * (o) mio[7] miosel[7] (1) card2csl * card2csl * (o) mio[6] miosel[6] (1) card2csh * card2csh * (o) mio[5] miosel[5] (1) card1wait * card1wait * (i) mio[4] miosel[4] (1) card2wait * card2wait * (i) mio[3] miosel[3] (1) carddir * carddir * (o) mio[2] miosel[2] (1) mfio[1] (reserved) mio[1] miosel[1] (1) mfio[0] (reserved) mio[0] miosel[0] (1) www.datasheet.in chapter 9 i/o module 9-7 table 9.2.2 and table 9.2.3 show the state of power down mode for multi-function i/o ports and i/o ports, respectively. table 9.2.2 multi-function i/o ports versus standard functions (power down state) power down state TMPR3911/12 pin standard function (i = input, o = output) standard function direction (1 = output, 0 = input) miopd=0 miosel=0 miodirec=x miopd=0 miosel=1 miodirec=0 miopd=0 miosel=1 miodirec=1 miopd=1 miosel=x miodirec=x chifs chifs (i/o) chifsdir chifs (i/o) hi-z miodout[31] pull-down chiclk chiclk (i/o) chiclkdir chiclk (i/o) hi-z miodout[30] pull-down chidout chidout (o) chienout chidout (o) hi-z miodout[29] pull-down chidin chidin (i) 0 hi-z hi-z miodout[28] pull-down dreq * dreq * (i) 0 hi-z hi-z miodout[27] pull-down dgrnt * dgrnt * (o) 1 0 hi-z miodout[26] pull-down bc32k bc32k (o) 1 bc32k (o) hi-z miodout[25] pull-down txd txd (o) 1 txd (o) hi-z miodout[24] pull-down rxd rxd (i) 0 hi-z hi-z miodout[23] pull-down cs1 * cs1 * (o) /powerdown hi-z hi-z miodout[22] pull-down cs2 * cs2 * (o) /powerdown hi-z hi-z miodout[21] pull-down cs3 * cs3 * (o) /powerdown hi-z hi-z miodout[20] pull-down mcs0 * mcs0 * (o) /powerdown hi-z hi-z miodout[19] pull-down mcs1 * mcs1 * (o) /powerdown hi-z hi-z miodout[18] pull-down mcs2 * mcs2 * (o) /powerdown hi-z hi-z miodout[17] pull-down mcs3 * mcs3 * (o) /powerdown hi-z hi-z miodout[16] pull-down spiclk spiclk (o) 1 spiclk (o) hi-z miodout[15] pull-down spiout spiout (o) 1 spiout (o) hi-z miodout[14] pull-down spiin spiin (i) 0 hi-z hi-z miodout[13] pull-down sibmclk sibmclk (i/o) sibmclkdir sibmclk (i/o) hi-z miodout[12] pull-down cardreg * cardreg * (o) 1 0 hi-z miodout[11] pull-down cardiowr * cardiowr * (o) 1 0 hi-z miodout[10] pull-down cardiord * cardiord * (o) 1 0 hi-z miodout[9] pull-down card1csl * card1csl * (o) /powerdown hi-z hi-z miodout[8] pull-down card1csh * card1csh * (o) /powerdown hi-z hi-z miodout[7] pull-down card2csl * card2csl * (o) /powerdown hi-z hi-z miodout[6] pull-down card2csh * card2csh * (o) /powerdown hi-z hi-z miodout[5] pull-down card1wait * card1wait * (i) 0 hi-z hi-z miodout[4] pull-down card2wait * card2wait * (i) 0 hi-z hi-z miodout[3] pull-down carddir * carddir * (o) 1 0 hi-z miodout[2] pull-down mfio[1] (reserved) ?? hi-z miodout[1] pull-down mfio[0] (reserved) ?? hi-z miodout[0] pull-down note: chifsdir, chiclkdir, sibmclkdir, powerdown: internal signal table 9.2.3 general purpose io (power down state) TMPR3911/12 pin iopd = 0 iodirec = 0 iopd = 0 iodirec = 1 iopd = 1 iodirec = x io[6] hi-z iodout[6] pull-down io[5] hi-z iodout[5] pull-down io[4] hi-z iodout[4] pull-down io[3] hi-z iodout[3] pull-down io[2] hi-z iodout[2] pull-down io[1] hi-z iodout[1] pull-down io[0] hi-z iodout[0] pull-down www.datasheet.in chapter 9 i/o module 9-8 9.2.4 related interrupts mfioposint[31:0]: issues an interrupt whenever any of the multi-function i/o pin(s) transition from a logic ?0? to a logic ?1?. there are a total of 32 multi-function i/o pins (31 thru 0), each of which corresponds to the respective bit within the interrupt status 3 register. each multi-function i/o pin can independently trigger an interrupt. mfionegint[31:0]: issues an interrupt whenever any of the multi-function i/o pin(s) transition from a logic ?1? to a logic ?0?. there are a total of 32 multi-function i/o pins (31 thru 0), each of which corresponds to the respective bit within the interrupt status 4 register. each multi-function i/o pin can independently trigger an interrupt. ioposint[6:0]: issues an interrupt whenever any of the general purpose i/o pin(s) transition from a logic ?0? to a logic ?1?. there are a total of 7 general purpose i/o pins (6 thru 0), each of which corresponds to the respective bit within the interrupt status 5 register. each general purpose i/o pin can independently trigger an interrupt. ionegint[6:0]: issues an interrupt whenever any of the general purpose i/o pin(s) transition from a logic ?1? to a logic ?0?. there are a total of 7 general purpose i/o pins (6 thru 0), each of which corresponds to the respective bit within the interrupt status 5 register. each general purpose i/o pin can independently trigger an interrupt. www.datasheet.in chapter 9 i/o module 9-9 9.3 i/o registers 9.3.1 i/o control register offset = $180: bit label reset read/write 31 reserved 31-24 iodebsel[6:0] x r/w 23 reserved 22-16 iodirec[6:0] 0 r/w 15 reserved 14-8 iodout[6:0] x r/w 7 reserved 6-0 iodin[6:0] ? r iodebsel[6:0]: these bits select the debounce mode for the 7 general purpose i/o pins. setting a specific bit location to a logic ?1? causes the respective general purpose i/o port signal to be filtered by a debounce circuit for the input signal direction. clearing a specific bit location to a logic ?0? causes the respective general purpose i/o port signal to bypass the input debounce circuit. iodirec[6:0]: these bits control the direction of the 7 general purpose i/o pins. setting a specific bit location to a logic ?1? configures the respective general purpose i/o pin to be an output. clearing a specific bit location to a logic ?0? configures the respective general purpose i/o pin to be an input. iodout[6:0]: these bits correspond to the data output values for the 7 general purpose i/o pins. setting or clearing a specific bit location controls the logic state of the respective general purpose i/o pin, if that pin is configured as an output. iodin[6:0]: read-only these bits correspond to the data input values for the 7 general purpose i/o pins. reading a specific bit location returns the logic state of the respective general purpose i/o pin, regardless of whether that pin is configured as an output or input. www.datasheet.in chapter 9 i/o module 9-10 9.3.2 mfio data output register offset = $184: bit label reset read/write 31-0 mfiodout[31:0] x r/w mfiodout[31:0]: these bits correspond to the data output values for the 32 multi-function i/o ports. setting or clearing a specific bit location controls the logic state of the respective multi-function i/o port, if that pin is configured as an output. 9.3.3 mfio direction register offset = $188: bit label reset read/write 31-0 mfiodirec[31:0] 0 r/w mfiodirec[31:0]: these bits control the direction of the 32 multi-function i/o ports. setting a specific bit location to a logic ?1? configures the respective multi-function i/o port to be an output. clearing a specific bit location to a logic ?0? configures the respective multi-function i/o port to be an input. 9.3.4 mfio data input register offset = $18c: read-only bit label reset read/write 31-0 mfiodin[31:0] ? r mfiodin[31:0]: read-only these bits correspond to the data input values for the 32 multi-function i/o pins. reading a specific bit location returns the logic state of the respective multi-function i/o pin, regardless of whether that pin is configured as an output or input. www.datasheet.in chapter 9 i/o module 9-11 9.3.5 mfio select register offset = $190: bit label reset read/write 31-0 mfiosel[31:0] $f20f0fff r/w mfiosel[31:0]: these bits correspond to the select mode for the 32 multi-function i/o pins. setting a specific bit location to a logic ?1? configures the respective multi-function i/o pin to be selected as a bi- directional i/o port. clearing a specific bit location to a logic ?0? configures the respective multi- function i/o pin to be selected as a standard/normal pin function. 9.3.6 i/o power-down register offset = $194: bit label reset read/write 31-7 reserved 6-0 iopd[6:0] $7f r/w iopd[6:0]: these bits control the power-down state for the 7 general purpose i/o pins. setting a specific bit location to a logic ?1? configures the respective general purpose i/o pin to power down when the TMPR3911/12 powers down. clearing a specific bit location to a logic ?0? configures the respective general purpose i/o pin to be in an active state at all times. 9.3.7 mfio power-down register offset = $198: bit label reset read/write 31-0 mfiopd[31:0] $faf03ffc r/w mfiopd[31:0]: these bits control the power-down state for the 32 multi-function i/o ports. setting a specific bit location to a logic ?1? configures the respective multi-function i/o port to power down when the TMPR3911/12 powers down. clearing a specific bit location to a logic ?0? configures the respective multi-function i/o port to be in an active state at all times. www.datasheet.in chapter 9 i/o module 9-12 www.datasheet.in chapter 10 ir module 10-1 10. ir module 10.1 overview the ir module consists of three parts. the first is the consumer interface, which provides an easy mechanism for generating pulses to either turn on or turn off a light emitting diode (led). the pattern in which the diode is turned on and off is used to encode commands which emulate remote control key presses that the consumer device recognizes. the software is responsible for programming the ir module parameters to emulate desired consumer remote control protocols and key presses. the consumer interface provides universal control of common consumer devices such as televisions, vcr?s, hi-fi equipment, appliances, etc. the second part of the ir module is the communication interface. the ir module can be used in one of two data communication modes: using a frequency shift keyed (fsk) modulation scheme or using a scheme based on the protocol standardized by the infrared data association (irda). the communication interface is implemented using a standard uart protocol with an adjustable baud rate. this interface operates half-duplex in one direction at a time. the uartb module is used for both the fsk and irda data communication modes (see section 16 for a detailed description of the uart module). for the fsk mode transmit direction, external communication ir analog circuitry encodes the uart output data using an fsk modulation scheme. for the receive direction, external communication ir analog circuitry amplifies the received photo-diode signal and demodulates the fsk signal before feeding the uart input. for the irda mode transmit direction, the uart output data directly drives the external analog led circuit. for the receive direction, the received photo-diode signal is externally amplified before feeding the uart input. additional control bits in the uart module also allow for various narrow pulse options to support the irda 1.0 standard. the final part of the ir module is the carrier detect state machine interface. this interface is used to periodically enable the receiver in the external communication ir analog circuitry to detect whether there is a valid carrier present. if a valid carrier is present then an interrupt will be issued so the system can begin receiving data. 10.1.1 related pins irout: output this pin is the uart transmit signal from the uartb module or the consumer ir output signal if consumer ir mode is enabled. irin: input this pin is the uart receive signal to the uartb module. rxpwr: output this pin is the receiver power output control signal to the external communication ir analog circuitry. cardet: input this pin is the carrier detect input signal from the external communication ir analog circuitry. www.datasheet.in chapter 10 ir module 10-2 10.2 consumer ir 10.2.1 requirements consumer ir remote controllers send a burst of pulses whenever a button is pressed. the number of bursts along with the length of each burst defines the key that has been pressed. burst of pulses no pulses number of bursts figure 10.2.1 consumer ir pulses the frequency of the pulses and the pulse width is fixed for a given remote control but can vary between different remote controls from different manufacturers. the number of pulses in a burst, the amount of time when there are no pulses, and the number of times that the burst is repeated are used to distinguish which key has been pressed for a given remote control. 10.2.2 implementation the consumer ir interface is designed to assist the cpu in shaping the pulses that are required to emulate a key press on a remote control. the logic has been implemented such that the frequency (typical consumer remote controllers use a carrier frequency in the 30 to 50 khz range) and width of a pulse can be programmed by the cpu for a given remote control. the processor can then vary the number of bursts in a pulse and the amount of time when there are no pulses on a byte by byte basis in order to emulate the various key presses. 10.2.3 block diagram ir master clock (irclk) 7-bit period number counter 1-bit on/off reg 8-bit pre scale counter irout 8-bit on-time width counter 2:1 mux 8-bit holding reg 16-bit ir holding reg baudval [7:0] per [7:0] ontime [7:0] txhold [15:0] 8-bit period width counter figure 10.2.2 consumer ir block diagram www.datasheet.in chapter 10 ir module 10-3 10.2.4 functional description the consumer ir logic remains idle until the cpu activates the ir logic by writing to the ir control 1 register to enable the consumer mode (enconsm = ?1?). prior to enabling the consumer mode, the cpu must configure the baud value (baudval), period value (per), and ontime value (ontime) fields located in the ir control 2 register. baudval[7:0] is used to pre-scale ir master clock (irclk) (since typical consumer ir data rates are in the khz range instead of the mhz range). per[7:0] is used to define the period of the pulses for a burst, representing the number of pre-scaled counts per period. ontime[7:0] defines the amount of time that the pulse is on for the given period, representing the number of pre-scaled counts for which the pulse is on. ontime should always be less than per or the irout signal will never transition low. transmit data = number of pulse and no-pulse width are written by the cpu into a 16-bit holding register, ir holding register, txhold field. when the 7-bit period number counter (down-counter) reaches zero, it will load the lower 7 bits of the holding register?s upper byte into the period number counter and the upper bit into the 1-bit on/off register. if the upper bit is set to a ?1? then the irout signal will be a ?1? until the ontime width counter reaches it?s terminal count. the ontime width counter freezes once it reaches it?s terminal count in order to prevent the signal from transitioning until the counter is loaded again. the irout signal will continue to transition according to the period value and ontime value until the 7-bit period number counter reaches zero. at this time the lower 7 bits of the holding register?s lower byte is loaded into the period number counter and the upper bit of the lower byte is loaded into the 1-bit on/off register. if the upper bit is set to a ?0? this time, then the irout signal will remain low for as many period counts as are defined by the value loaded into the 7-bit period number counter. thus the cpu controls the pulse generation by defining a number of pulses to burst (upper bit set to ?1?, lower 7-bit data defines the number of pulses) or an amount of time when there are no pulses (upper bit set to ?0?, lower 7-bit data defines the number of pulse times when irout is ?0?) on a byte by byte basis. the ontime value and period value timing relationships are shown in figure 10.2.3. period on time txhold u pp er bit = ?0? txhold u pp er bit = ?1? period = (per+1) (baudval+1) 1 f irclk on time = ontime (baudval+1) 1 f irclk figure 10.2.3 consumer ir signal generation 10.2.5 related interrupts irconsmint: whenever the upper byte of data is loaded into the 7-bit period number counter, the lower byte of data is loaded into an intermediate holding register. at this time the 16-bit ir holding register is empty. the irconsmint interrupt is then set to inform the cpu that the ir holding register is available. the cpu must fill the next word of data into the ir holding register before the 7-bit period number counter is finished counting the periods for both the upper and lower bytes of data. www.datasheet.in chapter 10 ir module 10-4 10.3 two-way communication via ir 10.3.1 requirements the communication interface is implemented using a standard uart protocol, consisting of a start bit, 8 bits of data (lsb first), then a stop bit. the data rate is adjustable using a programmable baud rate counter. the communication interface consists of both a transmitter and a receiver and the uart is operated half-duplex in one direction at a time. the uartb module is used for both the fsk and irda data communication modes and contains dma support for transmit and receive data (see section 16 for a detailed description of the uart module). for the fsk mode transmit direction, external communication ir analog circuitry encodes the uartb output data using an fsk modulation scheme, which modulates at two different frequencies depending on whether the data is a ?1? or a ?0?. the carrier frequency is 1375 khz and the mark and space frequencies are 1325 khz and 1425 khz, respectively. for the receive direction, external communication ir analog circuitry amplifies the received photo-diode signal and demodulates and decodes the fsk signal before feeding the uartb input. the transmitter and receiver portions of the external communication ir analog circuitry contain individual power-down control for power management purposes. the fsk communication mode operates at a data rate of 2400 to 38400 bps at 3 meters. for the irda mode transmit direction, the uartb output data directly drives the external analog led circuit. for the receive direction, the received photo-diode signal is externally amplified before feeding the uartb input. additional control bits in the uart module also allow for various narrow pulse options to support the irda 1.0 standard. when configured for these options, the uart transmit output pulses are narrower than normal and the uart receiver circuit also expects the same narrow pulse format for the input data. the irda communication mode operates at a data rate up to 115.2 kbps at 1 meter. www.datasheet.in chapter 10 ir module 10-5 10.3.2 block diagram external analog circuit TMPR3911/12 rxpwr cardet irin enmod * txpwr irout uartb module fsk mod led photodiode fsk demod figure 10.3.1 fsk communication circuit external analog circuit TMPR3911/12 irin irout uartb module led photodiode figure 10.3.2 irda communication circuit www.datasheet.in chapter 10 ir module 10-6 10.4 carrier detect state machine 10.4.1 requirements the external communication ir analog circuitry contains a circuit which detects if there is a valid carrier present. it is not desirable to leave this circuit enabled all the time because it dissipates too much power. thus the circuit is powered on and off with the rxpwr pin. it is possible for the cpu to periodically enable the rxpwr pin, then wait to see if a carrier is present (cardet pin = ?1?), but this requires a lot of processor overhead. in order to alleviate the overhead, the ir module contains a circuit that periodically enables the rxpwr pin, waits a specified period of time, samples the cardet pin, then disables the rxpwr pin. if the cardet pin is a ?1? when sampled then an interrupt is issued to the cpu indicating that there is a valid carrier present. after enabling the rxpwr pin the cardet pin cannot be sampled for a specified amount of time because the carrier detect logic in the external communication ir analog circuitry takes time to settle. the time between successive enabling of the rxpwr pin is programmable depending on the desired sample rate. wait value delay value valid carrier no valid carrier settle time settle time cardet rxpwr figure 10.4.1 carrier detect state timing 10.4.2 block diagram rxpwr 8-bit wait down counter 8-bit delay down counter 7.8 ms clock waitval (7:0) delayval (7:0) figure 10.4.2 carrier detect block diagram www.datasheet.in chapter 10 ir module 10-7 10.4.3 functional description delayval[7:0] is loaded into the 8-bit delay down counter whenever the counter reaches a count of zero. the terminal count of the delay down counter enables the 8-bit wait down counter which loads waitval[7:0] whenever the wait down counter reaches a count of zero. the rxpwr pin is asserted whenever the wait down counter reaches a count of zero. thus the period at which rxpwr is periodically asserted is derived by: (delayval + 1) * (waitval + 1) *7.8 ms the rxpwr pin will remain asserted until the wait down counter counts again which will occur at: (delayval + 1) *7.8 ms at the same time the rxpwr pin is deasserted the cardet pin is sampled and an interrupt is set if a valid carrier is present. 10.4.4 related interrupts carstint: this interrupt is set whenever the carrier detect state machine samples the cardet pin- = ?1? just before turning off the rxpwr pin. poscarint: this interrupt is set whenever cardet pin transitions from a logic ?0? to a logic ?1?. negcarint: this interrupt is set whenever cardet pin transitions from a logic ?1? to a logic ?0?. www.datasheet.in chapter 10 ir module 10-8 10.5 ir registers 10.5.1 ir control 1 register offset = $0a0: bit label reset read/write 31-25 reserved 24 cardet ? r 23-16 baudval[7:0] x r/w 15-5 reserved 4testir 0 r/w 3 dtinvert 0 r/w 2rxpwr 0 r/w 1 enstate 0 r/w 0 enconsm 0 r/w cardet: read-only this bit provides the status of the cardet (carrier detect) input pin. baudval[7:0]: these bits are used to pre-scale the ir master clock (irclk). the bits are loaded into an 8-bit down-counter that counts at the irclk rate. the resulting baud clock is used to clock the period width counter and ontime width counter. testir: this bit is used to speed up the counters for ic testing and should not be set. dtinvert: setting this bit to a logic ?1? will cause the irout signal to be active low instead of active high. rxpwr: this bit is connected to the rxpwr pin. enstate: setting this bit to a logic ?1? enables the communication ir carrier detect state machine. enconsm: setting this bit to a logic ?1? enables the consumer ir function. www.datasheet.in chapter 10 ir module 10-9 10.5.2 ir control 2 register offset = $0a4: write-only bit label reset read/write 31-24 per[7:0] x w 23-16 ontime[7:0] x w 15-8 delayval[7:0] x w 7-0 waitval[7:0] x w per[7:0]: write-only these bits are used to define the period of the consumer ir pulses. the bits are loaded into an 8- bit down-counter that counts at the rate defined by the baud value. the resulting period is given by the following equation. (f irclk is the frequency of the ir master clock (irclk).) period = (per + 1) * (baudval + 1) * (1/f irclk ) ontime[7:0]: write-only these bits are used to define the on time of the consumer ir pulses. these bits are loaded into an 8-bit down-counter that counts at the rate defined by the baud value. the resulting on time is given by the following equation. on time = ontime * (baudval + 1) * (1/f irclk ) delayval[7:0]: write-only these bits are used to define the amount of time that the rxpwr pin will be a logic ?1? when the carrier state machine logic is enabled. the bits are loaded into an 8-bit down-counter that counts at a 7.8 ms rate. thus the time is programmable from 7.8 ms to 2.0 seconds. delay time = (delayval + 1) *7.8 ms waitval[7:0]: write-only these bits are used to define the amount of time to wait before asserting the rxpwr pin to a logic ?1? when the carrier state machine logic is enabled. the bits are loaded into an 8-bit down- counter that counts whenever the delayval counter reaches a count of zero. thus the time is programmable from 7.8 ms to 511 seconds. wait time = (delayval + 1) * (waitval + 1) *7.8 ms www.datasheet.in chapter 10 ir module 10-10 10.5.3 ir holding register offset = $0a8: write-only bit label reset read/write 31-16 reserved 15-0 txhold[15:0] x w txhold[15:0]: write-only these bits are used to define the number of pulses in a burst or the amount of time to keep the irout pin low. the lower seven bits of the upper byte and the lower seven bits of the lower byte are used as values to load into a 7-bit counter that counts the number of periods as defined by the period value. the upper bit in each byte if set to a logic ?1? causes pulses on the irout pin and if set to a logic ?0? causes the irout pin to remain low for a given count. before setting the enconsm bit the txhold register must be pre-loaded with the first valid word of data. www.datasheet.in chapter 11 magicbus module 11-1 11. magicbus module 11.1 overview magic port is a multifunction expansion port for a wide range of serial peripheral connections. magicbus is a serial interface standard which includes an advanced communications protocol for interfacing to low- cost and low-power daisy-chainable peripherals and docks. the magicbus implementation is intended to support peripherals such as scanners, modems, battery chargers, base stations (including intelligent answering machines, telephones, fast chargers, etc.), storage devices, etc. magicbus features high-speed data transfer rates (up to 14.75 mbps), daisy-chainable peripherals (up to 6 maximum), and hot plugging. a low- cost magicbus interface circuit (mbic) is also available for use in peripherals. this interface can be implemented as a discrete circuit, as a standalone asic, or integrated with a microcontroller core (e.g., 68hc05 type). magicbus consists of a synchronous, serial two-wire (clock and data), half-duplex communications protocol. the clock and data signals are bi-directional, such that the TMPR3911/12 magicbus module can be dynamically configured as the bus master or slave at a given time. the protocol also includes an interrupt source for initiating all peripheral servicing, as well as when peripherals have been attached to or detached from the bus. TMPR3911/12?s magicbus module contains independent transmitter and receiver logic to implement the half-duplex serial data transfer, with dma support provided for both the transmit and receive directions. the independent transmitter and receiver allow a peripheral to control the data rate of the receiving shift register, since the receiver uses the peripheral?s transmit clock as it?s clock source. 11.1.1 related pins mbusclk: input/output this pin is the bi-directional magicbus clock signal. mbusclk is an input signal whenever the TMPR3911/12 is in the slave mode and is an output signal whenever the TMPR3911/12 is in the master mode. mbusdata: input/output this pin is the bi-directional magicbus data signal. mbusdata is an input signal whenever the TMPR3911/12 is in the slave mode and is an output signal whenever the TMPR3911/12 is in the master mode. mbusint: input this pin is the magicbus interrupt signal. this signal is used to interrupt the TMPR3911/12 whenever a peripheral has been attached to or detached from the bus, or whenever a peripheral has initiated an interrupt event. www.datasheet.in chapter 11 magicbus module 11-2 11.2 interface requirements 11.2.1 timing requirements magicbus consists of a synchronous, serial two-wire (clock and data), half-duplex communications protocol. the clock and data signals are bi-directional, such that the bus supports a single master at a given time, with all other bus members configured as slaves. the dynamic configuration of master versus slave assignments is controlled by the magicbus protocol. data is pushed onto the bus using the positive edge of mbusclk and the slaves sample the data using the negative edge of mbusclk, as shown in figure 11.2.1. mbusclk mbusdata figure 11.2.1 mbusdata and mbusclk timing 11.2.2 data formats magicbus commands and data sequences are comprised of groups of either 16-bit or 32-bit data, which are shifted serially with the most significant bit (msb) transmitted first in time. figure 11.2.2 shows the timing diagram for a 16-bit group of data. each of these 16-bit or 32-bit groups is shifted serially in either a seamless, non-interrupted fashion, or with delay inserted between every 8 bits, 16 bits, or 32 bits of the data stream. magicbus command words consist of 16-bit packets containing fields which specify information such as peripheral address, command code, and parity. all peripherals monitor and read these command words to determine whether they are the addressed peripheral and, if so, what is the exact command to be executed. b14 b13 b15 b0 b1 b2 mbusclk mbusdata figure 11.2.2 16-bit data group www.datasheet.in chapter 11 magicbus module 11-3 11.2.3 command words the magicbus protocol dictates that when a command word is to be transmitted, the clock and data signal functions are swapped, whereby mbusdata contains the clock signal and mbusclk contains the data signal. this swap mode is used to differentiate command words from ?raw data?. each peripheral mbic contains circuitry which detects whenever the clock and data signal functions have been swapped. the first 2 bits of each command word are command detection bits which re- synchronize the bus to reset the mode of any swapped clock/data lines and also prevent any past bus errors from corrupting current and future data transmissions. figure 11.2.3 shows a timing diagram of the command word and the swapping of the clock and data signal functions. command detection bits command word (swapped mode) previous packet mbusdata mbusclk b15 b0 b1 b2 b0 b1 figure 11.2.3 magicbus command word www.datasheet.in chapter 11 magicbus module 11-4 11.3 implementation 11.3.1 block diagram tx shift load rx hold load swap logic control/status from/to cpu mbus controll ogic dma addr half-buffer interrupt end-of-buffer interrupt buffer status interrupts control from cpu data to dma or cpu 16b/32b rx holding reg 16b/32b rx shift reg rx clock swap control tx clock 16b/32b tx shift reg 16b/32b tx holding reg 32 32 32 32 data from dma or cpu mbusclk mbusdata mbusint to interrupt module dma addr gen figure 11.3.1 magicbus module block diagram www.datasheet.in chapter 11 magicbus module 11-5 11.3.2 transmitter the magicbus transmitter consists of a holding register and shift register which support the serial data transmission from the magicbus module to attached magicbus peripheral devices. the 32-bit transmit holding register is loaded with parallel data from either the dma circuit or directly from the cpu. the magicbus module provides an interrupt (mbustxbufavailint) whenever the enmbus control bit is enabled or when the transmit holding register is available (i.e., empty). when the magicbus module is configured for long mode (long = ?1?), all 32 bits of the transmit holding register are valid. when the magicbus module is configured for word mode (long = ?0?), only the lower 16 bits of the transmit holding register are valid. the magicbus transmit holding register can be accessed at one of 2 address locations. one location corresponds to normal mode and the other location corresponds to swap mode. as mentioned previously, the swap mode is used for transferring command words, for which the clock and data signals are swapped. the contents of the transmit holding register then feed the 32-bit transmit shift register. this data is transferred in parallel whenever the transmit shift register is empty and available. the magicbus module provides an interrupt (mbusemptyint) whenever the transmit holding register and transmit shift register are both available (i.e., empty). the magicbus module also issues an interrupt (mbustxerrint) if the transmit holding register is written to when the holding register is not available (i.e., not empty). in this case, not enough time was provided for the contents of the transmit holding register to be transferred to the transmit shift register. the contents of the transmit shift register are then shifted out serially to the mbusdata output port (except for command words which use swap mode). when the magicbus module is configured for long mode (long = ?1?), all 32 bits of the transmit shift register are valid. when the magicbus module is configured for word mode (long = ?0?), only the first 16 bits of the transmit shift register are valid. the magicbus module supports 4 different combinations of clock polarity and phase, as determined by the clkpol and phapol control bits. figure 11.3.2 shows a timing diagram of the clock and data relationships for these 4 combinations. this flexibility allows data to be pushed and sampled on either the rising or falling edges of the clock. however, the actual magicbus protocol and specification specifies the use of only one of these combinations: clkpol = ?0? and phapol = ?1?, which means that mbusdata is always pushed on the rising edge of mbusclk and always sampled on the falling edge of mbusclk. b6 b3 b4 b5 b7 b0 b1 b2 mbusclk mbusclk mbusclk mbusclk clkpol = 1 phapol = 1 clkpol = 0 phapol = 1 clkpol = 1 phapol = 0 clkpol = 0 phapol = 0 mbusdata figure 11.3.2 magicbus clock and data relationships www.datasheet.in chapter 11 magicbus module 11-6 the transmit clock rate is also programmable, using the magicbus baud rate generator. the magicbus specification supports data rates from 250 kbps to 14.75 mbps. see section 11.3.4 for a detailed description of the magicbus baud rate generator. as mentioned previously, the transmit data consists of 16-bit or 32-bit groups. seamless operation is possible, whereby each data bit for each group is transmitted in a continuous and non-interrupted fashion. this seamless operation results in the fastest possible data rate for magicbus. in order to maintain seamless operation, the transmit holding register must be reloaded before the contents of the transmit shift register have been completely shifted out. in order to accommodate slower peripherals which cannot keep up with fast magicbus data rates, the magicbus module contains a programmable inter-packet delay counter. this counter allows the insertion of a programmable number of baud clocks of delay between bytes, words, or longs of the data stream, as shown in figure 11.3.3. see section 11.3.4 for a detailed description of the inter-packet delay counter. inter-packet delay figure 11.3.3 magicbus inter-packet delay 11.3.3 receiver the magicbus receiver consists of a shift register and holding register which support the receiving of serial data from attached magicbus peripheral devices to the magicbus module. data from the mbusdata input port is shifted in serially to the 32-bit receive shift register. the receive clock from the mbusclk port is used to clock the serial data through the receive shift register. this allows a peripheral to control the data rate of the magicbus receiver (allowing support for slower peripherals), since the receiver uses the peripheral?s transmit clock as it?s clock source. when the magicbus module is configured for long mode (long = ?1?), all 32 bits of the receive shift register are valid. when the magicbus module is configured for word mode (long = ?0?), only the first 16 bits of the receive shift register are valid. the contents of the receive shift register are then fed in parallel to the 32-bit receive holding register. the data is transferred whenever the receive shift register has finished shifting in either 16 or 32 bits of data depending on the selected mode. the receive holding register is read by either the dma circuit or directly by the cpu. the magicbus module provides an interrupt (mbusrxbufavailint) whenever the receive holding register is loaded with data (i.e., full). when the magicbus module is configured for long mode (long = ?1?), all 32 bits of the receive holding register are valid. when the magicbus module is configured for word mode (long = ?0?), only the lower 16 bits of the receive holding register are valid. the magicbus module issues an interrupt (mbusrxerrint) if the receive holding register is loaded twice from the receive shift register before the mbusrxbufavailint interrupt is serviced and the data in the receive holding register was never read. this situation might occur if the dma circuit or the cpu cannot keep up with the incoming data rate of the magicbus port. www.datasheet.in chapter 11 magicbus module 11-7 11.3.4 control logic the magicbus module contains several sets of counters which are used to generate the various internal control signals and clocks needed for the transmitter and receiver sections. a block diagram of the control logic is shown in figure 11.3.4. the enmbus control bit is used to enable the magicbus module by triggering the on/off logic circuit. when the enmbus control bit is deasserted to disable the magicbus module, the module will not shutdown until the transmit holding register and transmit shift register are empty plus a couple of magicbus baud clocks of delay. this allows the magicbus module to cleanly complete any pending transactions before shutdown of the module. the mbuson status bit indicates whether the magicbus module is still enabled or not. the programmable magicbus baud rate generator provides variable control of the transmit clock rate, as determined by the baudrate[7:0] control register value preloaded into the baud rate generator. the output of the baud rate generator is the magicbus baud clock, which is used to operate the transmit shift register and provides the mbusclk whenever TMPR3911/12 is configured as the magicbus bus master. the magicbus specification supports data rates from 250 kbps to 14.75 mbps. as mentioned previously, the magicbus module supports 4 different combinations of clock polarity and phase, as determined by the clkpol and phapol control bits. the magicbus specification specifies the use of only one of these combinations: clkpol = ?0? and phapol = ?1?, which means that mbusdata is always pushed on the rising edge of mbusclk and always sampled on the falling edge of mbusclk. the magicbus transmitter control logic consists of a transmit bit counter and a programmable transmit inter-packet delay counter. the transmit bit counter is used to count the number of bits to be shifted out the transmit shift register. this counter operates as a divide-by-16 (for word mode) or a divide-by-32 (for long mode), and is also used to generate the load pulse for transferring the contents of the transmit holding register to the transmit shift register. depending on the configuration of the enbytewait and enwordwait control bits, the transmit bit counter will also trigger the counting of the transmit inter-packet delay counter, which is used in order to accommodate slower peripherals which cannot keep up with fast magicbus data rates. this counter allows the insertion of a programmable number of baud clocks of delay (based on the delayval[7:0] control register value) between either bytes, words, or longs. delay is always inserted after each long (32-bit) group of bits, but is only inserted between bytes or words if the respective wait enable control bits (enbytewait and enwordwait) are asserted. in addition, if no delay is desired, then the delayval[7:0] register value should be set to ?0?. www.datasheet.in chapter 11 magicbus module 11-8 16/ 32 rx bit counter cmd word det logic rx buffer status logic decode rx cnt load logic decode 16/ 32 tx bit counter enbytewait enwordwait prgm tx inter- packet delay counter tx buff available int tx error int tx buff empty int rx buff available int rx hold load cmd word detect int baud clock word vs. long word vs. long 6 8 5 tx buffer status logic delay load logic dma logic on/off logic rx error int tx clock swap control shutdown tx shift load mbus dma req mbuson baudrate[7:0] delayval[7:0] rx clock enmbus prgm baud rate gen figure 11.3.4 magicbus control logic the magicbus receiver control logic consists of a receive bit counter and a circuit for detecting the receipt of a command word, whereby the clock and data signal functions are swapped. the magicbus receiver circuitry (including the receive bit counter and the receive shift register) uses the receive clock from the mbusclk port. this allows a peripheral to control the data rate of the magicbus receiver (allowing support for slower peripherals), since the receiver uses the peripheral?s transmit clock as it?s clock source. the receive bit counter is used to count the number of bits to be shifted into the receive shift register. this counter operates as a divide-by-16 (for word mode) or a divide-by-32 (for long mode), and is also used to generate the load pulse for transferring the contents of the receive shift register to the receive holding register. the command word detect logic monitors the mbusclk and mbusdata input lines and generates an interrupt (mbusdetint) whenever a command word is detected. www.datasheet.in chapter 11 magicbus module 11-9 11.3.5 dma address generation the magicbus module provides support for both transmit and receive dma. since the magicbus module operates half-duplex, a single dma channel is shared between transmit or receive, with only one direction using the buffer at a given time. the circuit used to generate the dma address, as well as half-buffer and end-of-buffer interrupts is shown in figure 11.3.5. the dma buffer size is programmable (up to a maximum of 1 mbyte) and the buffer start address is also programmable (anywhere over the full 32-bit address space). the dma buffer can be configured in a circular buffer mode or a one-time buffer mode, depending on the configuration of the endmaloop control bit. for the circular mode, the dma address is continuously incremented (each time a dma acknowledge is received from the TMPR3911/12?s central dma controller) and rolls over back to the start address after the end-of-buffer is reached and will continue operating in a continuous and circular manner. for the one-time mode, the dma logic will stop executing whenever the end-of-buffer is reached. half-buffer and end-of-buffer dma address counter interrupts are available, allowing the cpu to minimize overhead and utilize the dma buffer in a ping-pong fashion. for transmit mode, the cpu can use these interrupts to fill or write one half of the buffer while the other half is being emptied by the dma controller for transmitting magicbus data. similarly, for receive mode, the cpu can use these interrupts to empty or read one half of the buffer while the other half is being filled by the dma controller from received magicbus data. also available is a direct cpu read/write mode for bypassing the dma, allowing the cpu to read or write the magicbus data on a word by word (or long by long) basis, if so desired. separate dma enables are provided for receive and transmit. the dma circuit also provides the dma pointer status value, which is the actual 18-bit dma address counter output. this value indicates exactly where the current address is pointing to in the overall dma buffer, and is available via reading of the dmacnt[19:2] status register bits. end-of-buffer interrupt cnt load logic dma startval cntl peg control from cpu mbus cntl 1 peg dma length cntl peg 30 18 18 30 18 cmp addr cnt dma count dma addr half-buffer interrupt one-time vs. circular mode 2 cmp figure 11.3.5 magicbus dma address generation www.datasheet.in chapter 11 magicbus module 11-10 11.3.6 related interrupts mbustxbufavailint: this interrupt is set when the enmbus bit is first asserted and subsequently when the contents of the mbus transmitter holding register are transferred to the mbus shift register. this interrupt is used to indicate that the mbus transmitter holding register is available to be written by the software. mbustxerrint: issues an interrupt if the magicbus transmit holding register is written to when the transmit holding register is not available. mbusemptyint: issues an interrupt if the magicbus transmit holding register and transmit shift register are both empty. mbusrxbufavailint: issues an interrupt whenever the magicbus receive holding register is loaded with data. mbusrxerrint: issues an interrupt if the magicbus receive holding register is loaded twice before the interrupt is serviced. mbusdetint: issues an interrupt whenever the magicbus command word detector triggers. mbusdmafullint: issues an interrupt if the magicbus dma counter reaches the end of the buffer. mbusdmahalfint: issues an interrupt if the magicbus dma counter reaches the mid point of the buffer. mbusposint: issues an interrupt if whenever the mbusint signal goes from a logic ?0? to a logic ?1?. mbusnegint: issues an interrupt if whenever the mbusint signal goes from a logic ?1? to a logic ?0?. www.datasheet.in chapter 11 magicbus module 11-11 11.4 magicbus registers 11.4.1 magicbus control 1 register offset = $0e0: bit label reset read/write 31 mbuson 0 r 30 empty 1 r 29 mbusint ? r 28-17 reserved 16 endmarx 0 r/w 15 endmatx 0 r/w 14 endmatest 0 r/w 13 endmaloop 0 r/w 12 loopback 0 r/w 11 rcvphapol 0 r/w 10 dtidle 0 r/w 9 enbytewait 0 r/w 8enwordwait 0 r/w 7 detphapol 0 r/w 6 detclkpol 0 r/w 5 phapol 0 r/w 4 clkpol 0 r/w 3slave 0 r/w 2fslave 0 r/w 1long 0 r/w 0 enmbus 0 r/w mbuson: read-only when the enmbus bit is disabled, the module will not shutdown until the magicbus transmit holding register and transmit shift register are empty plus a couple of magicbus baud clocks of delay. this bit provides the status as to whether the module is still enabled or not. empty: read-only this bit is asserted if the magicbus transmit holding register and transmit shift register are both empty and the delay counter is finished inserting delay. mbusint: read-only this bit provides the status of the mbusint input pin. www.datasheet.in chapter 11 magicbus module 11-12 endmarx: this bit enables the dma receive function. this bit should not be set until the magicbus dma control 1 register and magicbus dma control 2 register are setup and the module is enabled. only one of endmarx or endmatx can be set at a time since there is only one dma channel. endmatx: this bit enables the dma transmit function. this bit should not be set until the magicbus dma control 1 register and magicbus dma control 2 register are setup, the module is enabled and the empty flag is set. only one of endmarx or endmatx can be set at a time since there is only one dma channel. endmatest: this bit is used for ic testing and should not be set. endmaloop: the dma controller supports two modes, depending on the state of this bit. when endmaloop is a logic ?0?, the dma controller will stop executing when it reaches the end of the dma buffer. when endmaloop is a logic ?1?, the dma controller will loop back to the start of the dma buffer when the end of the dma buffer is reached and will continue operating. loopback: setting this bit will cause the magicbus transmitter clock and data to be looped back into the receive clock and data. the data is inverted when this mode is selected. rcvphapol: setting this bit will cause the magicbus receiver clock to be inverted. dtidle: this bit defines the value that the mbusdata pin will idle to in between transmitted characters. enbytewait: setting this bit will cause a delay to be inserted between each byte in transmitted data. the length of the delay is defined by the value in the delayval bits. enwordwait: setting this bit will cause a delay to be inserted between each word in transmitted data. the length of the delay is defined by the value in the delayval bits. detphapol: setting this bit will cause the receive data pin to the command word clock to be inverted. detclkpol: setting this bit will cause the receive clock pin to the command word clear to be inverted. www.datasheet.in chapter 11 magicbus module 11-13 phapol: setting this bit will cause the magicbus transmitter to clock data out on the rising edge of mbusclk to be sampled by the peripherals on the falling edge of mbusclk. clkpol: setting this bit will invert the mbusclk pin. slave: setting this bit will cause the mbusclk and mbusdata pins to be inputs and will enable the magicbus receiver circuit. the transition from master to slave will not take place until the magicbus transmit holding register and transmit shift register are empty. fslave: setting this bit forces slave mode without regard to the status of the magicbus transmit holding register and transmit shift register. long: setting this bit will cause the magicbus transmitter and magicbus receiver to handle 32 bits per buffer. otherwise 16 bits is assumed. this bit must be set for dma transactions. enmbus: setting this bit will enable the magicbus module. when this bit is cleared the magicbus module is kept in a reset state. but clearing this bit gives no effect on the magicbus control register. this bit should not be set until all other control bits are setup. 11.4.2 magicbus control 2 register offset = $0e4: write-only bit label reset read/write 31-24 delayval[7:0] x w 23-16 baudrate[7:0] x w 15-0 reserved delayval[7:0]: write-only these bits define the number of magicbus baud clocks of delay to insert between either bytes, words, or longs. delay is always inserted after a long, but is only inserted between bytes or words if the respective enables (enbytewait or enwordwait) are set. if no delay is desired then the register should be set to zero. baudrate[7:0]: write-only these bits define the baudrate of the magicbus transmitter. the following equation determines the baudrate (f mbusmclk is the frequency of the magicbus master clock.): baudrate = f mbusmclk (baudrate[7:0] ? 2 + 2) www.datasheet.in chapter 11 magicbus module 11-14 11.4.3 magicbus dma control 1 register offset = $0e8: write-only bit label reset read/write 31-2 dmastartval[31:2] x w 1-0 reserved dmastartval[31:2]: write-only these bits define the start address for the dma buffer. 11.4.4 magicbus dma control 2 register offset = $0ec: write-only bit label reset read/write 31-20 reserved 19-2 dmalength[19:2] x w 1-0 reserved dmalength[19:2]: write-only these bits define the length of the dma buffer. the last address in the dma buffer is given by dmastartval[31:2] + dmalength[19:2]. the value loaded into dmalength should be equal to the desired buffer length ? 1. 11.4.5 magicbus dma count offset = $0f0: read-only bit label reset read/write 31-20 reserved 19-2 dmacnt[19:2] x r 1-0 reserved dmacnt[19:2]: read-only these bits provide the status of the dma counter. www.datasheet.in chapter 11 magicbus module 11-15 11.4.6 magicbus transmit holding register offset = $0f8: normal write-only offset = $0f4: swap write-only bit label reset read/write 31-0 txdata[31:0] x w txdata[31:0]: write-only these bits are the data to be transmitted. this register should only be loaded after the mbustxbufavailint interrupt is set. writing to the swap location will cause the clock and data lines to be swapped for this character of data. for word mode, only bits 15:0 are valid. 11.4.7 magicbus receive holding register offset = $0f8: read-only bit label reset read/write 31-0 rxdata[31:0] x r rxdata[31:0]: read-only these bits are the receive data. the bits are valid after the mbusrxbufavailint interrupt is set. for word mode, only bits 15:0 are valid. www.datasheet.in chapter 11 magicbus module 11-16 www.datasheet.in chapter 12 power module 12-1 12. power module 12.1 overview 12.1.1 system power control overview the system power supply must provide several power supplies to various parts of the system. the system may use the spi serial control interface, along with the pwrcs signal, to control turning on or off the various power supplies. the software will only turn on the power supplies that are required to perform a particular task. the TMPR3911/12 must always be provided power as long as there is a good main or backup battery in the system, or if a battery charger is plugged in. similarly, there may be other components in the system that must always be powered. these components, along with the TMPR3911/12, should be powered by the vstandby line. dram or sdram should be powered by the vccdram line. the vccdram power line should remain dead when the vstandby power line is first activated, until pwrcs is asserted to turn on the system for the first time. after the system boots for the first time, the software can decide not to turn off vccdram when the system is subsequently turned off, in order to preserve the contents of memory. most of the other components in the system, including rom, and system buffers are powered by the vcc3 line. the vcc3 power line is powered only when the system is on. other switchable power lines are provided for components such as the lcd, pc card, etc. each of these lines will normally be turned off by the software when powering down the system. when the system is on, these lines will only be turned on if the particular module is being used. in addition to the system power supply control, the power module also contains logic to support the TMPR3911/12 initialization, clock enable function, cpu stop mode, stop timer, and power failure logic. these features are described in detail in the following sub-sections. www.datasheet.in chapter 12 power module 12-2 12.1.2 power state transition diagram figure 12.1.1 shows the power state transition diagram of the TMPR3911/12 system. the details of transitions are described in he following subsections. power on reset state standby state battery backup state normal state suspend state onbutn & pwrok = high see 12.2.2 the 1st power up (by software) see 12.2.3 power down interrupt (by software) see 12.2.5 stop cpu pon * deassertion see 12.2.1 power on reset pwrok = low pwrok = high onbutn or interrupt see 12.2.4 power up (by software) see 12.2.3 power down figure 12.1.1 power state transition diagram www.datasheet.in chapter 12 power module 12-3 12.1.3 power supply lines in the system the description in this section assumes that the system has the following power supply lines. table 12.1.1 shows the status of each power supply line on each power state described in 12.1.2 in addition to these power supply lines a system power supply may provide other power supply lines according to particular system requirements. for example a system may have a dedicated power supply line for a pc card slot to supply power during the suspend state. vstandby: (vdd) this line provides power for the TMPR3911/12 and other components in the system that must never be powered off. this line should always be alive if there is either a good main battery or a good backup battery, or if a battery charger is plugged in. vccdram: this line provides power for the dram and/or sdram. this line must be off when vstandby is first powered, and remain off until the system is powered up by the assertion of pwrcs. when the software subsequently powers down the system it may choose to keep this line powered to preserve the contents of memory. vcc3: this line provides power for the rom, system buffers, and other components in the system. this line will be powered by the system power supply when pwrcs is asserted and will always be powered off when the system is powered down. table 12.1.1 power supply status power state power on reset state normal state standby state suspend state battery backup state vstandby on on on on on vccdram off on on on on vcc3 off on on off off www.datasheet.in chapter 12 power module 12-4 12.1.4 related pins pon*: input this pin serves as the power on reset signal for the TMPR3911/12. this signal must remain low when vstandby is asserted until vstandby is stable. once vstandby is powered, this signal should never go low unless all power is lost in the system. onbutn: input this pin is used as the on button for the system. asserting this signal will cause pwrcs to be asserted to request the system power supply to turn on the system power. pwrcs can not be asserted if the pwrok signal is low. pwrok: input this pin provides a status from the system power supply that there is a valid source of power in the system. this signal typically will be asserted if there is a battery charger supplying power or if the main battery is good and the battery door is closed. if the pwrok signal is low when the system is powered off, the pwrcs signal is not asserted by either the assertion of the onbutn signal or the interrupt detection. if the pwrok signal goes low while the device is on, the software should immediately shut down the system since power is about to be lost. when pwrok goes low, there must be serious warning so that the software can shut down the system before power is actually lost. when the pwroknmi bit in the interrupt status 6 register is set, the deassertion of the pwrok signal causes the nmi (non maskable interrupt). pwrcs: output this signal is asserted automatically if the onbutn signal is asserted when the pwrok signal is high. clearing the pwrcs bit in the power control register by software deasserts this signal. the usage of this signal depends on the implementation of the system power supply. for example, the assertion of this signal may usually cause the system power supply to turn vccdram and vcc3 on to power up the system. pwrint: input this pin is used by the system power supply to alert the software that some status has changed in the system power supply and the software should read the status from the system power supply to find out what has changed. these will be low priority events, unlike the pwrok status, which is a high priority emergency case. vcc3: input this pin provides the status of the power supply for the rom, system buffers, and other components in the system. this signal will be asserted by the system power supply when pwrcs is asserted, and will always be turned off when the system is powered down. www.datasheet.in chapter 12 power module 12-5 12.2 description 12.2.1 power on reset when vstandby is powered on, the pon* signal must be kept low until vstandby is stable, in order to provide a good power on reset to the TMPR3911/12. the assertion of pon* will set a reset flip-flop, as shown in figure 12.2.1. the reset flip-flop will remain set until the onbutn is pressed for the first time. this functionality provides a long reset time to the TMPR3911/12 when vstandby is first asserted. the long reset time is needed to allow the 32 khz oscillator to stabilize. the reset signal is used to initialize all registers and logic in the TMPR3911/12. figure 12.2.1 reset flip-flop onbutn pon * reset www.datasheet.in chapter 12 power module 12-6 12.2.2 the 1 st power up the 1 st power up sequence is shown in figure 12.2.2 when the onbutn is pressed, the pwrcs signal will be asserted if the pwrok signal is high. once the pwrcs signal is asserted, the system power supply powers vccdram and vcc3 in order to power up the system. once vcc3 is powered, the high frequency oscillator and pll that generate the clock signals for the cpu and biu start clocking. when the oscillator and pll are first enabled, the oscillation can vary widely until the oscillator and pll become stable. the stabilization time can vary between 1 ms and 10 ms, depending on the oscillator and pll of a particular TMPR3911/12 implementation. in order to prevent the TMPR3911/12 from using the clock before the clock becomes stable, a circuit in the power module will provide an internal signal ensysclk that will disable the clock until the oscillator and pll become stable. the circuit uses the 32 khz signal as its reference, since this is known to be good because of the long power on reset time. the ensysclk is asserted 16-24 ms after vcc3 is asserted at the 1 st power up. once the ensysclk signal is asserted, the cpu will start instruction execution. if the pwrok signal is low when the onbutn is pressed, the pwrcs signal will not be asserted. the ?pon* state? and the ?1 st -time power-up state? in the figure 12.2.2 are defined on page 2-17. c32k oscillator stabilization time min.1-2 s voltage stabilization time reset (internal) vcc3 (in) vstandby (system) pon * (in) pwrok (in) onbutn (in) pwrcs (out) 16-24 ms dclkout (out) ensysclk (internal) instruction execution 1 st time power-up state pon * state pin state figure 12.2.2 the 1 st power up sequence www.datasheet.in chapter 12 power module 12-7 12.2.3 power down a state transition into the suspend state is called ?power down?. typically this is triggered by assertion of the onbutn signal to power off the system. in the suspend state vstandby and vccdram are powered but vcc3 is not powered. some system may have some other power supply lines which are powered during the suspend state. for example a system may supply power to a pc card during the suspend state. if the system is powered up and the pwrok signal is deasserted, the system must be powered down as quickly as possible to preserve the contents of dram and/or sdram. all power supply lines, which are not required to preserve valuable data, must be powered off. this state is called the battery backup state. the system is powered down by software in the following sequence. 1. all modules in the TMPR3911/12 are disabled and all clocks in the clock module are turned off. 2. the interrupts for the wake-up events such as power switch, alarm (rtc), and serial dcd are enabled, and the other interrupts are disabled. when the pwrok signal is deasserted, some system may disable all interrupts to prevent unexpected power up after power will be supplied again. 3. the mempowerdown bit in the memory configuration 4 register is set in order to set the dram and/or sdram into self-refresh mode. the following instructions must be executed from cache memory. see section 0 for more details. 4. by clearing the pwrcs and vccon bits in the power control register simultaneously the pwrcs signal is deasserted. after the pwrcs is deasserted, the system power supply shuts down vcc3 power line. clearing vccon bit results in negating ensysclk and stopping all internal clocks except 32khz clock. a wait loop for a few milliseconds follows. a few instructions may be executed before power off. the rest of the wait loop is executed after the next power up to guarantee that some devices in the system are stable after power up. www.datasheet.in chapter 12 power module 12-8 12.2.4 power up when the system is off if rising edge of the onbutn signal or an enabled interrupt occurs, and the pwrok signal is asserted, then the system will power up. if assertion of the onbutn signal or an enabled interrupt occurs, but the pwrok signal is deasserted, then the system will not power up at that time. but since the interrupt is latched, the system will power up once the pwrok signal is asserted. on the other hand, the assertion of the onbutn signal is not a latched event unless the posonbutnint or negonbutnint interrupts are enabled. therefore, the assertion of the onbutn signal will not wake up the system once pwrok signal is asserted. once the ensysclk (internal signal) goes low, the clock to the cpu is stopped and the cpu will remain suspended at its last state. when the device powers back up, the ensysclk will be asserted 16-24 ms after vcc3 is asserted or 4-6 ms after vcc3 is asserted, depending on the state of the selc2ms control bit in the power control register. then the cpu will resume the instruction execution from where it stopped. it is probably desirable to loop for some time to make sure that the battery voltage has stabilized and the pwrok signal will not suddenly go low as a result of a substantial load added to the battery. once the loop has completed, the software must clear the forceshutdwn bit prior to accessing any address that is not in the cache or the internal function registers (see section 12.2.6). pwrok (in) onbutn (in) pwrcs (out) ensysclk (internal) dclkout (out) (mempowerdown: by software) (pwrcs/vccon: by software) interrupt delayed interrupt power down power up by delayed interrupt 16-24 ms or 4-6ms v cc3 (in) figure 12.2.3 power down and power up sequence www.datasheet.in chapter 12 power module 12-9 12.2.5 stop cpu in order to reduce the power consumption in the TMPR3911/12, it is desirable to stop the clock to the cpu when the cpu does not have to execute instructions. this is possible since the cpu core is fully static and will simply resume the instruction execution from where it stopped when the clock is re-enabled. the states in which just the cpu clock stops are called the standby state or the idle state. the system goes into the standby state by software in the following sequence. the iec bit in the status register of the cpu core is cleared to disable interrupt. 1. the software may change rf bits in the config register of the cpu core and slowbus bit in the power control register to reduce clock frequencies of dclkout, coreclk, clk2x, and clk (see section 6.2.1) for power saving. the reduced frequency must be determined to maintain the system activity (dma, peripheral device operation, etc.) in the standby state. 2. the software can stop the clock to the cpu by setting the stopcpu bit in the power control register. once this bit is set, the clock to the cpu will be stopped and remains stopped until an enabled interrupt clears the stopcpu bit. this bit should not be set when powering down the system because the ensysclk signal is a more dominant clock shutdown signal for the entire TMPR3911/12 chip. 3. a program loop waiting for the stopcpu bit to be set follows. some instructions are executed, then the cpu core stops. when any enabled interrupt events occur the system goes back to the normal state promptly. the following software sequence should be done. 1. the cpu core restarts the execution of the program loop waiting for the stopcpu bit to be cleared and exits from the loop promptly since the stopcpu bit is cleared. 2. resume the value of the rf bits and slowbus bit. 3. the iec bit in the status register of the cpu core is set to enable interrupt. 4. the cpu core jumps to the interrupt handler for the interrupt that waked up the system. the iec bit is used to resume the rf bits and slowbus bit before jumping to the interrupt handler. www.datasheet.in chapter 12 power module 12-10 12.2.6 forced shutdown the power module provides a feature called forced shutdown that will force the system to power down automatically if the pwrok signal goes low before the software clears the forceshutdwn bit. the main purpose of this feature is to protect the contents of dram or sdram. the timing sequence for forced shutdown is shown in figure 12.2.4. this feature can be enabled or disabled by setting the enforceshutdwn bit in the power control register. this feature is useful if a particular battery provides a pwrok indication when there is no load on the battery, but quickly deasserts the pwrok signal once the battery has some load by asserting vcc3. when this feature is disabled, the system will continue the instruction execution and enable the persistent memory even if the pwrok signal is deasserted, and will eventually stop by the power failure and lose the data in the memory. the forceshutdwn bit is set whenever pwrcs is asserted as a result of the onbutn being pressed or an enabled interrupt being set when the device is off. if the pwrok signal goes low prior to the software clearing the forceshutdwn bit, the power module will simply deassert the pwrcs signal and the system power supply will turn off the vcc3 power supply. the instruction to clear the forceshutdwn bit must be executed prior to bringing the memory interface out of self-refresh mode. this implies that the instruction has to be pre-loaded into the cache before the previous system shutdown, since the memory interface will exit self refresh mode once an address location is accessed in the system that is not in the cache or not to a function register. the very first time that the system is turned on after the assertion of vstandby, it is not possible to support this function since the cache is not initialized. this is not a problem because the main purpose of this feature is to protect the contents of dram or sdram, which does not exist when the device is turned on for the first time. pwrcs (out) forceshutdwn bit vcc3 (in) pwrok (in) onbutn (in) figure 12.2.4 forced shutdown sequence 12.2.7 memory power down by setting the mempowerdown bit in the memory configuration 4 register, the memory controller goes into memory power down mode. all memory signals will be driven low and drams and/or sdrams will go into self-refresh mode. the software can only access to the cache memory and the internal function registers. the first access outside them clears the mempowerdown bit and drams and/or sdrams will go out of the self-refresh mode. thus it is necessary that all instructions following the assertion of the mempowerdown bit need to be executed on the cache memories. 12.2.8 stop timer the stop timer is used as a coarse timer to bring the cpu out of stop mode. the stop timer consists of a 4-bit up counter and a comparator to generate the stptimerint interrupt. the stop timer is enabled using the enstptimer control bit in the power control register. when the enstptimer control bit is not set the counter will be reset to zero. once the enstptimer bit is set the counter will count up using an 8 ms clock as the input. once the counter reaches a value that is equal to the stptimerval[3:0] control bits, the stptimerint interrupt is set. the stop timer will provide a maximum duration of 120 ms, in steps of 8 ms. www.datasheet.in chapter 12 power module 12-11 12.2.9 power module interrupts stptimerint: this interrupt is set whenever the stop timer counter counts up to the value set by the stptimerval[3:0] control bits. pospwrint: this interrupt is set when the pwrint pin changes from a logic ?0? to a logic ?1?. negpwrint: this interrupt is set when the pwrint pin changes from a logic ?1? to a logic ?0?. pospwrokint: issues an interrupt whenever the pwrok signal changes from a logic ?0? to a logic ?1?. negpwrokint: issues an interrupt whenever the pwrok signal changes from a logic ?1? to a logic ?0?. posonbutnint: issues an interrupt whenever the onbutn signal changes from a logic ?0? to a logic ?1?. if the dbnconbutn control bit is set then the interrupt will not be set until the signal is debounced for 16-24 ms. negonbutnint: issues an interrupt whenever the onbutn signal changes from a logic ?1? to a logic ?0?. if the dbnconbutn control bit is set then the interrupt will not be set until the signal is debounced for 16-24 ms. www.datasheet.in chapter 12 power module 12-12 12.3 power registers 12.3.1 power control register offset = $ 1c4: bit label reset read/write 31 onbutn ? r 30 pwrint ? r 29 pwrok ? r 28-27 vidrf[1:0] 0 r/w 26 slowbus 0 r/w 25 divmod 0 r/w 24-16 reserved 15-12 stptimerval[3:0] x r/w 11 enstptimer 0 r/w 10 enforceshutdwn 0 r/w 9 forceshutdwn 0 r/w 8 forceshutdwnocc 0 r/w 7selc2ms 0 r/w 6 reserved 5 bpdbvcc3 0 r/w 4stopcpu 0 r/w 3 dbnconbutn 0 r/w 2coldstart 1 r/w 1pwrcs 0 r/w 0 vccon 0 r/w onbutn: read-only this bit provides the status of the onbutn signal. pwrint: read-only this bit provides the status of the pwrint signal. pwrok: read-only this bit provides the status of the pwrok signal. stptimerval[3:0]: when the stop timer is enabled the stptimerint interrupt will be set when the counter is equal to the value set by these bits. enstptimer: this bit is used to enable the stop timer. vidrf[1:0]: these bits select the divide-ratio of vidclk, which is the master clock used for the video module. vidrf divide-ratio 01 12 24 38 www.datasheet.in chapter 12 power module 12-13 slowbus: setting this bit will cause the internal clocks except freeclk and xhfee to be divided by 2. divmod: setting this bit will cause the clocks in each function module such as an uart to be independent of rf (1:0). (see section 6, figure 6.2.1 and 6.2.2) enforceshutdwn: the forceshutdwn bit is set whenever the vccon bit and the pwrcs bit are set by either the onbutn signal assertion or an enabled interrupt occurrence. if the pwrok signal goes low before the processor clears the forceshutdwn bit, then the vccon bit and the pwrcs bit are cleared and the pwrcs signal will go low if the enforceshutdwn bit is set. if the enforceshutdwn bit is not set, then the forceshutdwn bit will have no effect. forceshutdwn: if the enforceshutdwn bit is set, then this bit must be cleared after the initial boot, but prior to memory interface waking up procedure. see section 12.2.6 for details. forceshutdwnocc: this bit is set if a forced shutdown occurs due to the pwrok signal going low prior to the processor clearing the forceshutdwn bit. this bit provides status to the processor to indicate that the event occurred. the bit should be cleared once the status has been checked, so that it can be used again for the next power up. selc2ms: the assertion of pwrcs signal will cause the system power supply to assert the vcc3 power line. once vcc3 is powered, the oscillator and pll inside of the TMPR3911/12 will wake up and generate the main system clock, but for a certain period of time the clock will be unstable until the oscillator and pll lock on the correct frequency. the power module will prevent the clock from driving any logic until the clock becomes stable. the reference clock for the debouncing delay time is provided by the c2ms (2 ms clock) and the c8ms (8 ms clock) internal signals generated by the rtc from the 32 khz oscillator. if selc2ms is set to a logic ?1?, the clock will be disabled for a minimum of 4 ms and a maximum of 6 ms after vcc3 is powered. if selc2ms is set to a logic ?0?, the clock will be deasserted for a minimum of 16 ms and a maximum of 24 ms after vcc3 is powered. bpdbvcc3: if this bit is set, the clock will be enabled immediately following the assertion of vcc3, instead of waiting for the delay mentioned in the selc2ms bit description. stopcpu: setting this bit will cause the clock to the cpu core to be disabled to allow low power operation. the bit is cleared whenever an enabled interrupt is set. this bit should not be set when powering down the system. it is only used when the system is powered up, but the cpu does not have to execute instructions. www.datasheet.in chapter 12 power module 12-14 dbnconbutn: if this bit is set, then the posonbutnint and negonbutnint interrupts and the onbutn wake up function will only occur after a minimum of 16 ms and a maximum of 24 ms of debouncing of the onbutn signal has taken place to allow direct ?undebounced? button connection. if this bit is cleared, then the interrupts and power up occur immediately upon transition of the onbutn signal. coldstart: this bit is set by reset and provides status to the processor that a power on reset has occurred. pwrcs: this bit is set whenever the onbutn signal is asserted or an enabled interrupt occurs while the pwrok signal is high. when powering down the system, this bit must be cleared simultaneously with the vccon bit. all enabled interrupts must be cleared prior to powering down the system, or the pwrcs and vccon signals will not go low. vccon: this bit is set whenever the onbutn is pressed or an enabled interrupt occurs if the pwrok signal is high. when powering down the system, this bit must be cleared simultaneously with the pwrcs bit. all enabled interrupts must be cleared prior to powering down the system, or the pwrcs and vccon signals will not go low. www.datasheet.in chapter 13 sib module 13-1 13. sib module 13.1 overview the sib module within the TMPR3911/12 contains holding registers, shift registers, and other logic to support interfacing to the analog-front-end device: tc35143 and/or other optional external codec devices. the overall sound subsystem for a pic (personal information communicator) allows playing and recording of sounds, and consists of a single-channel 12-bit codec within tc35143, tc35143 interface circuits for direct connection to an external microphone (mic) and speaker, and dma support within the TMPR3911/12. similarly, the overall telecom subsystem for a pic allows support of high-performance software modems, and consists of a single-channel 16-bit codec within tc35143, which also includes optional echo cancellation and interface circuits for connection to an external data access arrangement (daa), as well as an auxiliary input/output port for supporting future wireless interfaces. the daa provides the front-end interface circuitry needed between the analog telephone network and the telecom codec for wireline configurations. the front-end circuit can also include ring detect, off-hook detect, and connect detect functions. audio and telecom data and control/status information (such as sampling rate, gain control, muting, clip detect, etc.) is passed between the TMPR3911/12 and tc35143 (and/or other external codec devices) via the sib. within the TMPR3911/12, the sib module logic provides dma support and control/status registers for data transfers between external system memory, the cpu core, and the sib. sib data transfer is always synchronous and is frame-based, with the TMPR3911/12 side always the master source of the clock and frame frequency and phase. for the sound subsystem, tc35143 allows the system to digitize (using the sound codec?s adc) the mic input, as well as to convert (using the sound codec?s dac) sampled sounds (either pre-stored, synthesized, or previously recorded) stored in system memory to an analog audio output, for routing to either a speaker and/or headphone output. for the telecom subsystem, tc35143 allows the system to digitize (using the telecom codec?s adc) the telecom analog baseband receive input, and the subsequent modem baseband signal processing can be implemented using entirely a software-based approach. tc35143 then allows the system to convert (using the telecom codec?s dac) the processed baseband transmit output to an analog telecom output for routing back out the wireline or wireless port. the sib module provides full-duplex dma support for sound receive and transmit, as well as independent dma support for telecom receive and transmit (four total independent dma channels). the dma buffers can be configured in a continuous (circular) buffer mode or a one-time (empty or fill, then stop) buffer mode. half-buffer and end-of-buffer dma address counter interrupts are available, allowing the cpu to minimize overhead and efficiently empty or fill half of the dma buffer in a ping-pong fashion. the dma buffer size is programmable (up to a maximum of 16 kbytes) and the receive and transmit buffers can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). also available is a direct cpu read/write mode for bypassing the dma, allowing the cpu to read or write the sound or telecom data on a sample by sample basis, if so desired. www.datasheet.in chapter 13 sib module 13-2 13.1.1 related pins sibdin: input this pin contains the input data shifted from tc35143 and/or external codec device. sibdout: output this pin contains the output data shifted to tc35143 and/or external codec device. sibsclk: output this pin is the serial clock sent to tc35143 and/or external codec device to synchronize the data transfer. sibsync: output this pin is the frame synchronization signal sent to tc35143 and/or external codec device. this frame sync is asserted for one clock cycle immediately before each frame starts and all devices connected to the sib monitor sibsync to determine when they should transmit or receive data. sibirq: input this pin is a general purpose input port used for the sib interrupt source from tc35143. this interrupt source can be configured to generate an interrupt on either a positive and/or negative edge. sibmclk: input/output this pin is the master clock source for the sib logic. this pin can be used as output mode or input mode. in output mode, sibmclk can be configured as a high-rate output master clock source required by certain external codec devices. in this mode all sib clocks are synchronously slaved to the main TMPR3911/12 system clock clk2x. in input mode, sibmclk can be configured as an input slave clock source. in this mode, all sib clocks are derived from an external sibmclk oscillator source, which is asynchronous with respect to clk2x. also, for this mode, sibmclk can still be optionally used as a high-rate master clock source required by certain external codec devices. www.datasheet.in chapter 13 sib module 13-3 13.2 block diagram telecom tx hold reg control tx hold reg mux mode control from cpu data from cpu data from dma or cpu telecom rx hold reg status rx hold reg sound rx hold reg half-buffer interrupt end-of-buffer interrupt dma addr clock and sync gen x2 (sound and telecom) dma addr gen clk clk 32 32 clk2x sibout sibdin sibmclk sibsclk sibsync data to cpu data from dma or cpu control from cpu control from cpu 32 32 sound tx hold reg mux 64-bit shift reg figure 13.2.1 sib module block diagram www.datasheet.in chapter 13 sib module 13-4 13.2.1 holding and shift registers the sib module logic consists of holding registers (both transmit and receive) and a serial shift register to support the transfer of sound and telecom data and control/status information between the TMPR3911/12 and tc35143 (and/or other external codec devices) via the sib (see figure 13.2.1 for a block diagram of the sib module). for the sib transmit direction, the sound and telecom transmit holding registers are written either from the dma circuit or directly from the cpu, while the subframe 0 and subframe 1 control holding registers are always written directly from the cpu. these holding registers are processed by an array of multiplexers which select which fields of the various 32-bit transmit holding registers are loaded into the 64-bit shift register, such that an entire subframe is loaded in parallel and then shifted out the serial output sibdout. the sequence of loading the shift register from the various holding register fields is determined by the programmed sound and telecom sample rates, mono versus stereo mode, and 8-bit versus 16-bit modes. conversely, for the sib receive direction, the sound and telecom receive holding registers are read either by the dma circuit or directly by the cpu, while the subframe 0 and subframe 1 status holding registers are always read directly by the cpu. the 64-bit shift register containing an entire subframe of received data from the serial input sibdin is processed by an array of multiplexers which select which fields of the various 32-bit receive holding registers are loaded from the shift register. the sequence of loading the various fields of the receive holding registers from the shift register is determined by the programmed sound and telecom sample rates, mono versus stereo mode, left versus right mono source, and 8-bit versus 16-bit modes. 13.2.2 clock and sync generation the sib module logic contains several programmable counters which are used to generate the various sib internal and external control signals and clocks. see figure 13.2.2 for a block diagram of the sib clock and sync generation circuit. as mentioned previously, sibmclk can be configured as either an input or output. as an output, sibmclk is derived by dividing down from clk2x. in this mode, all sib clocks are then synchronously slaved to the main TMPR3911/12 system clock and only one main xtal source is required for the entire system (besides the 32 khz rtc xtal), resulting in the lowest cost system configuration with regards to clock sources. as an input, sibmclk is generated from an external oscillator source, which is asynchronous with respect to clk2x. this more expensive configuration allows the sib (and also potentially the chi and dual-uart circuits) to operate independent of the frequency used for the cpu core. this allows flexible system design options with respect to the cpu operating frequency, along with the ability to generate the required or desired uart baud rates and audio/telecom sampling frequencies. the programmable sibsclk rate is derived by dividing down from sibmclk. nominal rates for a tc35143-only configuration are clk2x 5 (tmpr3912au-92/xb-92) and sibsclk = 9.216 mhz (equals sibmclk 2). the sibsclk rate is then used to enable a set of counters (word counter and subframe/frame counter) to generate the sibsync frame rate of 72 khz (equals sibsclk 128), as well as various internal sib clocks and control signals. the subframe rate is used to enable independent sets of programmable sound and telecom sample rate counters which generate various control signals based on the desired sample rates. for instance, this logic correctly generates the sound and telecom valid flag bits which are asserted within the sibdout serial output stream every time a valid sample is being transmitted. www.datasheet.in chapter 13 sib module 13-5 snd start/stop control tel start/stop control sib shift reg control sib holding reg control sib dma reg control tel vflag tel frame cnt tel sample interrupt snd vflag snd frame cnt snd sample interrupt sibsync sibsclk clk clk2x sibmclk prgm divider control from cpu decode decode 32 word cnt prgm divider prgm snd fs cnt 6 sf/frame cnt prgm tel fs cnt decode figure 13.2.2 sib clock and sync generation www.datasheet.in chapter 13 sib module 13-6 13.3 interface requirements 13.3.1 frame structure each sib frame consists of 128 sibsclk, further divided into 2 subframes: subframe 0 and 1. the sib frame structure is shown in figure 13.3.1. subframe 0 subframe 1 1 frame sibsync sibsclk sibdin sibdout figure 13.3.1 sib framing structure 13.3.2 timing requirements the TMPR3911/12 always samples receive data (sibdin) on the falling edge of sibsclk, whereas the transmit data from tc35143 is always output on the rising edge of sibsclk. similarly, the TMPR3911/12 always output transmit data (sibdout) on the rising edge of sibsclk, whereas the transmit data to tc35143 is always sampled on the falling edge of sibsclk in tc35143. the sibsync signal is asserted for one sibclk cycle immediately before each frame starts and all devices connected to the sib monitor sibsync to determine when they should transmit or receive data. sibsync is always sampled by tc35143 on the falling edge of sibsclk. the timing relationship for the sibsclk, sibsync, and data signals (sibdin, sibdout) is shown in figure 13.3.2. 2 1 63 subframe 1 start frame start sibdout sibdin sibsync sibsclk subframe 0 062630 subframe 1 figure 13.3.2 sib timing relationships www.datasheet.in chapter 13 sib module 13-7 13.3.3 configurations many configuration options exist for the sib. the sib module control bits selsndsf1 and seltelsf1 are used to determine the desired sib configuration. see table 13.3.1 for a summary matrix of these possible configurations. the lowest cost configuration utilizes tc35143 only, assigned to subframe 0 of the sib, while subframe 1 is not used. for this configuration, the system utilizes the audio and telecom codecs within tc35143. the sibsclk rate is fixed and the independent sound and telecom sample rates are controlled via TMPR3911/12 and tc35143 programmable counters. table 13.3.1 sib configuration matrix (1) tmpr3912au-92/xb-92; 11.520 mhz crystal to be used. rf[1:0] = 00, slowbus = 0. sound codec telecom codec tmpr3912 clk2x [1] sibsclk sibmclk out or sound osc in [2] sib frame rate [3] comments tc35143; fs = 8k, 11.05k, 16k, or 22.15k tc35143; fs = 7.2k, 8k, or 9.6k 92.16m 9.216m ( 10) 18.432m out ( 5) 72k tc35143 only; lowest cost; sibsclk = fixed; sound & telecom fs control; via tc35143 prgm [4]; sib subframe0 = tc35143; sib subframe1 = not used; selsndsf1 = 0; seltelsf1 = 0; table 13.3.2 sib configuration matrix (2) the TMPR3911bu/bxb sib does not provide support for a 7.3728-mhz crystal. to use the sib, use a 6.912-mhz crystal. rf[1:0]=00, slowbus=0. sound codec telecom codec tmpr3912 clk2x [1] sibsclk sibmclk out or sound osc in [2] sib frame rate[3] comments tc35143; fs = 8 k 11.05 k, 16 k, or 22.15 k tc35143; fs = 7.2 k, 8 k, or 9.6 k 55.296 m 9.216 m ( 6) 18.432 m out ( 3) 72 k tc35143 only; lowest cost; sibsclk = fixed; sound & telecom fs control; via tc35143 prgm [4]; sib subframe1 = not used; selsndsf1 = 0; seltelsf1 = 0; notes : [1] TMPR3911/12 clk2x is internal high-rate system-wide clock [2] optional external sound osc can be connected to TMPR3911/12 sibmclk (to allow decoupling of sib clocks from clk2x; else this pin can be configured as buffered sibmclk output which is synchronously divided down from clk2x (sibmclk allows potential support of codecs requiring a high-rate fixed master clock + a sample-rate-dependent serial clock); sibsclk serial clock is always synchronously divided down from sibmclk [3] sib frame rate = sibsclk 128; ratio for average number of sib-frames per valid-data-frame is dependent upon sound & telecom fs [4] tc35143 audio/telecom fs divider programmability: sib-frame/valid-data-frame ratio (sibsclk 2) (40 64) = 7.2k 5 (sibsclk 2) (36 64) = 8k 4.5 (sibsclk 2) (30 64) = 9.6k 3.75 (sibsclk 2) (15 64) = 19.2k (1.6% error vs. 18.9k for cd-xa) 1.875 (sibsclk 2) (13 64) = 22.154k (0.47% error vs. 22.050k for cd-audio) 1.625 (sibsclk 2) (12 64) = 24k 1.5 www.datasheet.in chapter 13 sib module 13-8 13.3.4 sample rates the sndfsdiv and telfsdiv control bits are used to independently configure the sampling rate for the audio and telecom codecs, respectively. these control bits set the modulus of the audio and telecom sample rate counters within the sib module. tc35143 also contains its own set of audio and telecom sample rate counters for its internal use and these counters must be both frequency and phase synchronized to the sample rate counters within the TMPR3911/12 in order to guarantee correct operation. the synchronization of these counters is triggered from the codec enable command transmitted by the TMPR3911/12 and received by tc35143, as shown in figure 13.3.3. the sample rate is calculated using the following (note that the fsdiv value loaded into the counter is the desired count modulus ? 1): fs = (sibsclk 2) ((fsdiv + 1) 64) for example, if sibsclk = 9.216 mhz and fsdiv = 39 (modulo 40), then: fs = (9.216 mhz 2) ((39 + 1) 64) = 7.2 khz www.datasheet.in chapter 13 sib module 13-9 0 1 2 4 5 6 0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 2 3 5 6 4 3 sf0 sf1 sib frame sibsclk/32 sibssync (note 4) ( note 2 ) (note 3) (note 1) valid sample flag valid sample trigger fs count (modulo-7 example) codec enable note 1: during this frame, audio (and/or telecom) codec input or output enable command is transmitted by TMPR3911/12 and receive d by tc35143f note 2: at start of first frame after codec is enabled, audio (and/or telecom) counters are reset; this ensures that TMPR3911/12 and tc35143f fs counters are immediately phase-synchronized note 3: during this frame, first valid dac sample is transmitted by TMPR3911/12 (received by tc35143f) or first valid adc sample is transmitted by tc35143f (received by TMPR3911/12); valid dac and adc samples are always transmitted during the same subframe (full duplex) note 4: audio (and/or telecom) vflag bits are asserted to tc35143f for one subframe each time a new dac sample is being transmit ted (TMPR3911/12 will also latch a new adc sample from tc35143f during the same subframe); since the audio (and/or telecom) programmable sample rate is derived from sibsclk/32 (= 4x frame rate), valid samples are synchronized from the periodic fs coun t rollover to the next available sib subframe above timing diagram shows fs count and valid sample flag generation for example configuration where frequency divisor = 6 (m o dulo-7 divide). figure 13.3.3 sib sample rate setup timing www.datasheet.in chapter 13 sib module 13-10 13.3.5 enable/disable sequencing as mentioned in the previous section, the synchronization of the sample rate counters within TMPR3911/12 and tc35143 is triggered from the codec enable command transmitted by TMPR3911/12 and received by tc35143. the following steps illustrate the full sequence of events needed to enable and disable the audio and/or telecom processing paths, while ensuring synchronization of these sample rate counters (the example below shows a configuration with tc35143 for sound and telecom, using subframe 0 only): initial enable sequence: (1) sib is initially disabled (ensib = 0) (2) setup sib control registers to desired settings (sib clock rates, sample rate dividers, data formats (8-bit vs. 16-bit, etc.), dma settings, subframe 0 enable = ensf0 (3) write initial data and control values to transmit holding registers (sndtxhold, teltxhold, sf0aux); sf0aux control register sets up tc35143 audio and telecom codecs, including sample rate dividers (to match TMPR3911/12 sample rates), gains, etc. codecs are not enabled at this point (4) enable sib (assert ensib = 1) (5) sib then begins transmitting and receiving data; tc35143 control registers get configured with desired settings; codecs still not enabled at this point snd (or tel) enable sequence: (6) setup software to trigger from sibsf0int (7) immediately after sibsf0int trigger, software must write to sf0aux to assert audio (or telecom) codec enable, and during same subframe (i.e., before sibsf1int event occurs), software must assert ensnd (or entel) (8) after next sibsf0int and during the subframe 0 period, the codec enable command is transmitted from TMPR3911/12 and received by tc35143 (9) the audio (or telecom) codec within tc35143 is then enabled at the start of the next frame after the enable command is sent, at which time the sample rate counters within both TMPR3911/12 and tc35143 begin counting in a synchronized fashion (10) during this first frame after codec is enabled, the first dac sample is transmitted by TMPR3911/12 (received by tc35143) and/or the first adc sample is transmitted by tc35143 (received by TMPR3911/12); dac and adc samples are always transmitted during the same subframe in a full-duplex manner (as mentioned in the previous section, dac and adc samples are synchronized from the periodic sample rate counter rollover to the next available sib subframe) (11) check valid status from tc35143 (indicates whether adc?s are settled, all turn-on delays have been met, etc.) which indicates valid samples snd (or tel) disable sequence: (12) software writes to sf0aux to de-assert audio (or telecom) codec enable, in order to disable codec (13) software then de-asserts ensnd (or entel) to disable sound (or telecom) processing on TMPR3911/12 side www.datasheet.in chapter 13 sib module 13-11 13.3.6 data formats the TMPR3911/12?s sib module logic contains transmit and receive holding registers which are used by the dma circuit or cpu to write and read sound and telecom data and sib control and status register data. the sndtxhold and sndrxhold registers are used for transmit and receive sound data corresponding to the appropriate subframe (0 or 1), according to the configuration as determined by the selsndsf1 control bit. similarly, the teltxhold and telrxhold registers are used for transmit and receive telecom data corresponding to the appropriate subframe (0 or 1), according to the configuration as determined by the seltelsf1 control bit. all of these holding registers are 32 bits wide, and the appropriate shift register fields for each subframe are written to or read from based on the programmed sound and telecom samples rates, mono versus stereo mode, and 8-bit versus 16-bit modes. the sf0aux and sf1aux control holding registers and sf0stat and sf1stat status holding registers are also 32 bits wide. each of these control holding registers updates the control fields for the respective subframe once per frame. these transmit holding registers load the same control data into the shift register until the cpu updates the contents of the holding register. similarly, the status holding registers are updated from the received status data in the shift register once per frame. the contents of the receive holding registers are available to be read by the cpu at any time. the sib data format for transfers to and from tc35143 is shown in figure 13.3.4. each word consists of fields containing audio data, telecom data, and control register address and data. during each frame, data is transferred bi-directionally (using sibdin and sibdout) for all of these fields. for instance, the audio data field is written once every frame (from the TMPR3911/12 to tc35143) via sibdout and also returns audio data (from tc35143 to the TMPR3911/12) at the same time via sibdin. 016324864 register data[15:0] audio data[11:0] telecom data[15:0] write audio vflag telecom vflag register addr[3:0] figure 13.3.4 data format for tc35143 word interface www.datasheet.in chapter 13 sib module 13-12 the sf0aux control holding register and sf0stat status holding register map directly to bits 16-31 and 48-63 of the subframe 0 word format. see table 13.3.3 which shows the mapping of sf0aux and sf0stat bit positions to the respective tc35143 fields. for tc35143, the audio and telecom ?vflag? bits (valid flags) in the transmit direction are dynamically asserted to tc35143 for one subframe each time a new sample is being transmitted. the audio and telecom ?vflag? bits in the receive direction are statically asserted from tc35143 to the TMPR3911/12 only after the adc?s are settled, all turn-on delays have been met, etc. the TMPR3911/12 then uses these valid flags to determine when the receive data from tc35143 is truly valid. table 13.3.3 sib subframe 0 control/status bits and fields sf0aux/sf0stat bits tc35143 word bits field definition - - - 0-15 audio data 31 16 reserved for register extension; must write to 0 if not used 30-27 17-20 register address[3:0] 26 21 write bit 25-18 22-29 reserved, must write to 0 17 30 audio valid flag 16 31 telecom valid flag - - - 32-47 telecom data 15-0 48-63 register data[15:0] the last 16 bits of the tc35143 word is made up of control register data. the exact contents and definition of this field is defined by the register address field and the ?write? bit. for a read cycle (?write? bit = 0), the address bits determine which tc35143 register to read and this read data is sent by tc35143 within the control register data field of sibdin during the same frame as the read request occurred. the separation between the address and data fields should make this possible. in addition, during a read cycle, the control register data field of sibdout is ignored by tc35143. for a write cycle (?write? bit = 1), the control register data contents of sibdout are written to the tc35143 register pointed to by the register address field. 13.3.7 subframe formats sib subframe 0 is nominally reserved for interfacing to tc35143. four possible sample-size modes are supported for sound and telecom data (these are all mono sound and telecom formats): sound telecom 16-bit 16-bit 16-bit 8-bit 8-bit 16-bit 8-bit 8-bit sib subframe 1 is nominally reserved for interfacing to an external codec device. for the external codec device, four possible sample-size modes are supported: sound telecom 16-bit stereo 16-bit 16-bit mono 8-bit 8-bit stereo 8-bit mono www.datasheet.in chapter 13 sib module 13-13 table 13.3.4 sib holding and shift register formats (subframe 0) subframe 0 sound 16 bit, telecom 16 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:16] sf0aux[31:18], vs, vt teltxhold[31:16] sf0aux[15:0] 1 sndtxhold[15:0] sf0aux[31:18], vs, vt teltxhold[15:0] sf0aux[15:0] 2 sndtxhold[31:16] sf0aux[31:18], vs, vt teltxhold[31:16] sf0aux[15:0] 3 sndtxhold[15:0] sf0aux[31:18], vs, vt teltxhold[15:0] sf0aux[15:0] subframe 0 sound 16 bit, telecom 8 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:16] sf0aux[31:18], vs, vt teltxhold[31:24], 8b0sf0aux[15:0] 1 sndtxhold[15:0] sf0aux[31:18], vs, vt teltxhold[23:16], 8b0 sf0aux[15:0] 2 sndtxhold[31:16] sf0aux[31:18], vs, vt teltxhold[15:8], 8b0 sf0aux[15:0] 3 sndtxhold[15:0] sf0aux[31:18], vs, vt teltxhold[7:0], 8b0 sf0aux[15:0] subframe 0 sound 8 bit, telecom 16 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:24], 8b0 sf0aux[31:18], vs, vt teltxhold[31:16] sf0aux[15:0] 1 sndtxhold[23:16], 8b0 sf0aux[31:18], vs, vt teltxhold[15:0] sf0aux[15:0] 2 sndtxhold[15:8], 8b0 sf0aux[31:18], vs, vt teltxhold[31:16] sf0aux[15:0] 3 sndtxhold[7:0], 8b0 sf0aux[31:18], vs, vt teltxhold[15:0] sf0aux[15:0] subframe 0 sound 8 bit, telecom 8 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:24], 8b0 sf0aux[31:18], vs, vt teltxhold[31:24], 8b0 sf0aux[15:0] 1 sndtxhold[23:16], 8b0 sf0aux[31:18], vs, vt teltxhold[23:16], 8b0 sf0aux[15:0] 2 sndtxhold[15:8], 8b0 sf0aux[31:18], vs, vt teltxhold[15:8], 8b0 sf0aux[15:0] 3 sndtxhold[7:0], 8b0 sf0aux[31:18], vs, vt teltxhold[7:0], 8b0 sf0aux[15:0] note: ?vs? = valid sound flag bit; ?vt? = valid telecom flag bit ?8b0? = 8-bit field of zero values ?sr? = shift register www.datasheet.in chapter 13 sib module 13-14 table 13.3.5 sib holding and shift register formats (subframe 1 sound) subframe 1 sound 16 bit stereo: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:16] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] 1 sndtxhold[31:16] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] 2 sndtxhold[31:16] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] 3 sndtxhold[31:16] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] subframe 1 sound 16 bit mono: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:16] sf1aux[31:16] sndtxhold[31:16] sf1aux[15:0] 1 sndtxhold[15:0] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] 2 sndtxhold[31:16] sf1aux[31:16] sndtxhold[31:16] sf1aux[15:0] 3 sndtxhold[15:0] sf1aux[31:16] sndtxhold[15:0] sf1aux[15:0] subframe 1 sound 8 bit stereo: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:24], 8b0 sf1aux[31:16] sndtxhold[23:16], 8b0 sf1aux[15:0] 1 sndtxhold[15:8], 8b0 sf1aux[31:16] sndtxhold[7:0], 8b0 sf1aux[15:0] 2 sndtxhold[31:24], 8b0 sf1aux[31:16] sndtxhold[23:16], 8b0 sf1aux[15:0] 3 sndtxhold[15:8], 8b0 sf1aux[31:16] sndtxhold[7:0], 8b0 sf1aux[15:0] subframe 1 sound 8 bit mono: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 sndtxhold[31:24], 8b0 sf1aux[31:16] sndtxhold[31:24], 8b0 sf1aux[15:0] 1 sndtxhold[23:16], 8b0 sf1aux[31:16] sndtxhold[23:16], 8b0 sf1aux[15:0] 2 sndtxhold[15:8], 8b0 sf1aux[31:16] sndtxhold[15:8], 8b0 sf1aux[15:0] 3 sndtxhold[7:0], 8b0 sf1aux[31:16] sndtxhold[7:0], 8b0 sf1aux[15:0] note: ?8b0? = 8-bit field of zero values ?sr? = shift register table 13.3.6 sib holding and shift register formats (subframe 1 telecom) subframe 1 telecom 16 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 16b0 sf1aux[31:17], vt teltxhold[31:16] sf1aux[15:0] 1 16b0 sf1aux[31:17], vt teltxhold[15:8] sf1aux[15:0] 2 16b0 sf1aux[31:17], vt teltxhold[31:16] sf1aux[15:0] 3 16b0 sf1aux[31:17], vt teltxhold[15:8] sf1aux[15:0] subframe 1 telecom 8 bit: frame sr[64:49] sr[48:33] sr[32:17] sr[16:1] 0 16b0 sf1aux[31:17], vt teltxhold[31:24], 8b0 sf1aux[15:0] 1 16b0 sf1aux[31:17], vt teltxhold[23:16], 8b0 sf1aux[15:0] 2 16b0 sf1aux[31:17], vt teltxhold[15:8], 8b0 sf1aux[15:0] 3 16b0 sf1aux[31:17], vt teltxhold[7:0], 8b0 sf1aux[15:0] note: ?vs? = valid sound flag bit; ?vt? = valid telecom flag bit ?8b0? = 8-bit field of zero values; ?16b0? = 16-bit field of zero values ?sr? = shift register www.datasheet.in chapter 13 sib module 13-15 13.4 dma address generation the sib module provides support for four independent dma channels: sound receive and transmit and telecom receive and transmit. two identical circuits (one for sound dma and one for telecom dma) are used to generate the dma address, as well as half-buffer and end-of-buffer interrupts (see figure 13.4.1). the dma buffer size is programmable (up to a maximum of 16 kbytes) and the receive and transmit buffer start addresses are also programmable (anywhere over the full 32-bit address space). because there are separate start addresses, the receive and transmit buffers can be configured to either reside in different memory spaces or share the same memory space. the latter setup allows for overlapping buffers for loopback purposes or for optimum memory allocation, for which the dma logic supports two full-duplex loopback modes. for one mode, receive dma requests are issued first, followed by transmit dma requests. this ordering allows a receive-to-transmit immediate loopback via the dma buffer. for the second mode, transmit dma requests are issued first, followed by receive dma requests. thus, received samples are written to the dma buffer location immediately after transmit samples were read from that same location (which then became immediately available). this ordering allows a single circular dma buffer to be used for both transmit and receive samples. the dma buffers can be configured in a circular buffer mode or a one-time buffer mode. for the circular mode, the dma address is continuously incremented (each time a dma acknowledge is received from the TMPR3911/12?s central dma controller) and rolls over back to the start address after the end-of-buffer is reached and will continue operating in a continuous and circular manner. for the one-time mode, the dma logic will stop executing whenever the end-of-buffer is reached. half-buffer and end-of-buffer dma address counter interrupts are available, allowing the cpu to minimize overhead and utilize the dma buffer in a ping-pong fashion. for transmit mode, the cpu can use these interrupts to fill or write one half of the buffer while the other half is being emptied by the dma controller for transmitting out the sib. similarly, for receive mode, the cpu can use these interrupts to empty or read one half of the buffer while the other half is being filled by the dma controller from received sib input samples. also available is a direct cpu read/write mode for bypassing the dma, allowing the cpu to read or write the sound or telecom data on a sample by sample basis, if so desired. separate dma enables for receive and transmit allow dma to be setup for receive only (transmit via cpu), transmit only (receive via cpu), receive and transmit, or none (receive and transmit via cpu). the sound and telecom dma circuits also provide an interrupt each time the respective dma buffer pointer is incremented, which occurs whenever a new sample is read from and/or written to the dma buffer. this interrupt may be useful for triggering a read of the dma pointer status value, which is the actual 12-bit dma address counter output. this value indicates exactly where the current address is pointing to in the overall dma buffer. www.datasheet.in chapter 13 sib module 13-16 2 cmp cmp one-time vs. circular mode dma rd/wr mode half-buffer interrupt cnt load logic 30 end-of-buffer interrupt dma addr dma pointer clk addr cnt 2:1 12 12 12 30 rx start addr control from cpu tx start addr dma cntl reg buffer size figure 13.4.1 sib dma address generation www.datasheet.in chapter 13 sib module 13-17 13.5 related interrupts snd0_5int: issues an interrupt whenever the sound dma buffer pointer has reached the halfway point. snd1_0int: issues an interrupt whenever the sound dma buffer pointer has reached the end-of-buffer point. tel0_5int: issues an interrupt whenever the telecom dma buffer pointer has reached the halfway point. tel1_0int: issues an interrupt whenever the telecom dma buffer pointer has reached the end-of-buffer point. snddmacntint: issues an interrupt each time the sound dma buffer pointer is incremented, which occurs whenever a new sound sample is read from and/or written to the sound dma buffer. teldmacntint: issues an interrupt each time the telecom dma buffer pointer is incremented, which occurs whenever a new telecom sample is read from and/or written to the telecom dma buffer. lsndclipint: issues an interrupt whenever the amplitude of the left channel sound data is clipping the codec a/d converter for sib subframe 1. rsndclipint: issues an interrupt whenever the amplitude of the right channel sound data is clipping the codec a/d converter for sib subframe 1. valsndposint: issues an interrupt whenever the valid sound status flag transitions from a logic ?0? to a logic ?1?. this valid flag is triggered from sib subframe 0 (if selsndsf1 = ?0?) or from sib subframe 1 (if selsndsf1 = ?1?). valsndnegint: issues an interrupt whenever the valid sound status flag transitions from a logic ?1? to a logic ?0?. this valid flag is triggered from sib subframe 0 (if selsndsf1 = ?0?) or from sib subframe 1 (if selsndsf1 = ?1?). va lt e l p o s i n t: issues an interrupt whenever the valid telecom status flag transitions from a logic ?0? to a logic ?1?. this valid flag is triggered from sib subframe 0 (if seltelsf1 = ?0?) or from sib subframe 1 (if seltelsf1 = ?1?). www.datasheet.in chapter 13 sib module 13-18 valtelnegint: issues an interrupt whenever the valid telecom status flag transitions from a logic ?1? to a logic ?0?. this valid flag is triggered from sib subframe 0 (if seltelsf1 = ?0?) or from sib subframe 1 (if seltelsf1 = ?1?). sndinint: issues an interrupt whenever a valid sound input longword (32 bits) is available from the sound rx holding register; this also means a valid sound output longword can be written to the sound tx holding register. telinint: issues an interrupt whenever a valid telecom input longword (32 bits) is available from the telecom rx holding register; this also means a valid telecom output longword can be written to the telecom tx holding register. sibsf0int: issues an interrupt at the start of every sib subframe 0. this is used to initiate cpu reading of the sib subframe 1 status register (sf1stat register) and/or cpu writing of the sib subframe 0 control register (sf0aux register). sibsf1int: issues an interrupt at the start of every sib subframe 1. this is used to initiate cpu reading of the sib subframe 0 status register (sf0stat register) and/or cpu writing of the sib subframe 1 control register (sf1aux register). sibirqposint: issues an interrupt whenever the sibirq pin transitions from a logic ?0? to a logic ?1?. sibirqnegint: issues an interrupt whenever the sibirq pin transitions from a logic ?1? to a logic ?0?. www.datasheet.in chapter 13 sib module 13-19 13.6 sib registers 13.6.1 sib size register offset = $060: write-only bit label reset read/write 31-30 reserved 29-18 sndsize[13:2] x w 17-14 reserved 13-2 telsize[13:2] x w 1-0 reserved sndsize[13:2]: write-only these bits define the size of the sound dma buffers (16 kbytes maximum). both the sound rx buffer and the sound tx buffer are the same size. the last address in the sound rx dma buffer is given by sndrxstart[31:2] + sndsize[13:2]. the last address in the sound tx dma buffer is given by sndtxstart[31:2] + sndsize[13:2]. the value loaded into sndsize should be equal to the desired buffer length ? 1. note that this register is write only. telsize[13:2]: write-only these bits define the size of the telecom dma buffers (16 kbytes maximum). both the telecom rx buffer and the telecom tx buffer are the same size. the last address in the telecom rx dma buffer is given by telrxstart[31:2] + telsize[13:2]. the last address in the telecom tx dma buffer is given by teltxstart[31:2] + telsize[13:2]. the value loaded into telsize should be equal to the desired buffer length ? 1. note that this register is write only. 13.6.2 sib sound rx start register offset = $064: write-only bit label reset read/write 31-2 sndrxstart[31:2] x w 1-0 reserved sndrxstart[31:2]: write-only these bits define the start address for the sound rx dma buffer. the sound rx buffer and sound tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). www.datasheet.in chapter 13 sib module 13-20 13.6.3 sib sound tx start register offset = $068: write-only bit label reset read/write 31-2 sndtxstart[31:2] x w 1-0 reserved sndtxstart[31:2]: write-only these bits define the start address for the sound tx dma buffer. the sound rx buffer and sound tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). 13.6.4 sib telecom rx start register offset = $06c: write-only bit label reset read/write 31-2 telrxstart[31:2] x w 1-0 reserved telrxstart[31:2]: write-only these bits define the start address for the telecom rx dma buffer. the telecom rx buffer and telecom tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). 13.6.5 sib telecom tx start register offset = $070: write-only bit label reset read/write 31-2 teltxstart[31:2] x w 1-0 reserved teltxstart[31:2]: write-only these bits define the start address for the telecom tx dma buffer. the telecom rx buffer and telecom tx buffer can be configured to either reside in different memory spaces or share the same memory space (overlapping buffers for loopback purposes or for optimum memory allocation). www.datasheet.in chapter 13 sib module 13-21 13.6.6 sib control register offset = $074: bit label reset read/write 31 sibirq ? r 30 encnttest 0 r/w 29 endmatest 0 r/w 28 sndmono x r/w 27 rmonosndin x r/w 26-24 sibsclkdiv[2:0] x r/w 23 tel16 x r/w 22-16 telfsdiv[6:0] x r/w 15 snd16 x r/w 14-8 sndfsdiv[6:0] x r/w 7seltelsf1 x r/w 6 selsndsf1 x r/w 5entel 0 r/w 4 ensnd 0 r/w 3 sibloop 0 r/w 2ensf1 0 r/w 1ensf0 0 r/w 0 ensib 0 r/w sibirq: read-only this bit provides the logic state of the sibirq input pin. the sibirq pin is active-high from tc35143. encnttest: this bit is used for ic testing and should not be set. endmatest: this bit is used for ic testing and should not be set. sndmono: this bit is used to configure the sound input and output format for sib subframe 1 as mono versus stereo. setting this bit to a logic ?1? selects mono mode. clearing this bit to a logic ?0? selects stereo mode. rmonosndin: this bit is used to select left versus right channel as the mono sound source for sib subframe 1, whenever the sound is configured as mono mode. setting this bit to a logic ?1? selects the right channel as the mono sound source. clearing this bit to a logic ?0? selects the left channel as the mono sound source. www.datasheet.in chapter 13 sib module 13-22 sibsclkdiv[2:0]: these bits select the start count value and the stop count value for the 4-bit programmable counter used to generate sibsclk, which is derived by dividing down sibmclk; sibsclk is the serial bit clock used for the sib. since the msb of the counter output is used for sibsclk, the start count and stop count values are chosen to provide (as close as possible) a 50% duty cycle sibsclk. the table used to compute these counter start and stop values are as follows: sibsclkdiv start value stop value divide-modulus 0782 1683 2694 3595 45106 54118 6 3 12 10 7 2 13 12 tel16: this bit is used to configure the sib telecom input and output format as 8-bit versus 16-bit mode. setting this bit to a logic ?1? selects 16-bit mode. clearing this bit to a logic ?0? selects 8-bit mode. telfsdiv[6:0]: these bits select the divider modulus for the 7-bit programmable counter used to generate the telecom sample rate clock, which is derived by dividing down an internal sib clock of rate equal to the 4 times the sib frame rate or 2 times the sib subframe rate (where each frame consists of 128 serial data bits). this programmable divider consists of a down-counter which counts down from telfsdiv to zero, so the value loaded for telfsdiv should be the desired divider modulus ? 1. for example, if sibmclk = 18.432 mhz and sibsclk = 9.216 mhz ( = sibmclk 2), in order to generate a telecom sample rate of 7.2 khz, the value loaded for telfsdiv should = 39, since 9.216 mhz (40 32) = 7.2 khz. www.datasheet.in chapter 13 sib module 13-23 snd16: this bit is used to configure the sib sound input and output format as 8-bit versus 16-bit mode. setting this bit to a logic ?1? selects 16-bit mode. clearing this bit to a logic ?0? selects 8-bit mode. sndfsdiv[6:0]: these bits select the divider modulus for the 7-bit programmable counter used to generate the sound sample rate clock, which is derived by dividing down an internal sib clock of rate equal to the 4 times the sib frame rate or 2 times the sib subframe rate (where each frame consists of 128 serial data bits). this programmable divider consists of a down-counter which counts down from sndfsdiv to zero, so the value loaded for sndfsdiv should be the desired divider modulus ? 1. for example, if sibmclk = 18.432 mhz and sibsclk = 9.216 mhz ( = sibmclk 2), in order to generate a sound sample rate of 24 khz, the value loaded for sndfsdiv should = 11, since 9.216 mhz (12 32) = 24 khz. seltelsf1: this bit is used to select between sib subframe 0 and subframe 1 for the telecom data source and destination. setting this bit to a logic ?1? selects sib subframe 1 as the telecom source. clearing this bit to a logic ?0? selects sib subframe 0 as the telecom source. selsndsf1: this bit is used to select between sib subframe 0 and subframe 1 for the sound data source and destination. setting this bit to a logic ?1? selects sib subframe 1 as the sound source. clearing this bit to a logic ?0? selects sib subframe 0 as the sound source. entel: this bit is used to enable/disable telecom processing for the sib module. setting this bit to a logic ?1? enables telecom processing. clearing this bit to a logic ?0? disables telecom processing. this bit should not be set until after the sib module is setup, then ensib asserted. special timing restrictions are required whenever an enable/disable command is sent to tc35143 and/or other external codec device (see figure 13.3.3). first, after sibsf0int (if seltelsf1 = ?0?) or sibsf1int (if seltelsf1 = ?1?) is asserted, the cpu then writes a telecom codec enable command to tc35143 via the sf0aux (if seltelsf1 = ?0?) or sf1aux (if seltelsf1 = ?1?) register. the cpu then asserts entel. both of these cpu transactions must occur within the same sib frame period, which is before the next sibsf0int (if seltelsf1 = ?0?) or sibsf1int (if seltelsf1 = ?0?). this ensures that the sample rate counters within the TMPR3911/12 and tc35143 are fully phase-synchronized. www.datasheet.in chapter 13 sib module 13-24 ensnd: this bit is used to enable/disable sound processing for this sib module. setting this bit to a logic ?1? enables sound processing. clearing this bit to a logic ?0? disables sound processing. this bit should not be set until after the sib module is setup, then ensib asserted. special timing restrictions are required whenever an enable/disable command is sent to tc35143 and/or other external codec device (see figure 13.3.3). first, after sibsf0int (if selsndsf1 = ?0?) or sibsf1int (if selsndsf1 = ?1?) is asserted, the cpu then writes a sound codec enable command to tc35143 via the sf0aux (if selsndsf1 = ?0?) or sf1aux (if selsndsf1 = ?1?) register. the cpu then asserts ensnd. both of these cpu transactions must occur within the same sib frame period, which is before the next sibsf0int (if selsndsf1 = ?0?) or sibsf1int (if selsndsf1 = ?0?). this ensures that the sample rate counters within the TMPR3911/12 and tc35143 are fully phase-synchronized. sibloop: this bit is used for ic testing and should not be set. setting this bit to a logic ?1? will cause the sib serial transmitted data to be internally looped back to the sib serial receive data path. the data is inverted when this mode is selected. setting this bit to a logic ?0? selects the normal sibdin pin as the sib serial receive data source. ensf1: this bit is used to enable/disable sib subframe 1 processing. setting this bit to a logic ?1? enables sib subframe 1. clearing this bit to a logic ?0? disables sib subframe 1, causing the sib serial transmitted data during this subframe to be zeroed and all received data during this subframe to not be processed by the sib module. this bit should be set before ensib is asserted. ensf0: this bit is used to enable/disable sib subframe 0 processing. setting this bit to a logic ?1? enables sib subframe 0. clearing this bit to a logic ?0? disables sib subframe 0, causing the sib serial transmitted data during this subframe to be zeroed and all received data during this subframe to not be processed by the sib module. this bit should be set before ensib is asserted. ensib: this bit is used to enable/disable the sib module. setting this bit to a logic ?1? enables the sib module. clearing this bit to a logic ?0? disables the sib module and keeps the module in a reset state but gives no effect on the sib control register. www.datasheet.in chapter 13 sib module 13-25 13.6.7 sib sound tx holding register offset = $078: write-only bit label reset read/write 31-0 sndtxhold[31:0] x w sndtxhold[31:0]: write-only these bits represent the sound data to be transmitted. sound data can be either written directly to this register by the cpu or transparently read from the sound tx dma buffer to this register. this register should only be loaded by the cpu after the sndinint interrupt is asserted. the sound and telecom data processing can be configured from among several possible formats (mono versus stereo and 8-bit versus 16-bit data formats); see table 13.3.4 13.3.3 for a summary of these formats. 13.6.8 sib sound rx holding register offset = $078: read-only bit label reset read/write 31-0 sndrxhold[31:0] ? r sndrxhold[31:0]: read-only these bits represent the sound data to be received. sound data can be either read directly from this register by the cpu or transparently written to the sound rx dma buffer from this register. this register should only be read by the cpu after the sndinint interrupt is set. the sound and telecom data processing can be configured from among several possible formats (mono versus stereo and 8-bit versus 16-bit data formats); see table 13.3.4 13.3.3 for a summary of these formats. 13.6.9 sib telecom tx holding register offset = $07c: write-only bit label reset read/write 31-0 teltxhold[31:0] x w teltxhold[31:0]: write-only these bits represent the telecom data to be transmitted. telecom data can be either written directly to this register by the cpu or transparently read from the telecom tx dma buffer to this register. this register should only be loaded by the cpu after the telinint interrupt is asserted. the sound and telecom data processing can be configured from among several possible formats (mono versus stereo and 8-bit versus 16-bit data formats); see table 13.3.4 13.3.7 for a summary of these formats. www.datasheet.in chapter 13 sib module 13-26 13.6.10 sib telecom rx holding register offset = $07c: read-only bit label reset read/write 31-0 telrxhold[31:0] ? r telrxhold[31:0]: read-only these bits represent the telecom data to be received. telecom data can be either read directly from this register by the cpu or transparently written to the telecom rx dma buffer from this register. this register should only be read by the cpu after the telinint interrupt is set. the sound and telecom data processing can be configured from among several possible formats (mono versus stereo and 8-bit versus 16-bit data formats); see table 13.3.4 13.3.7 for a summary of these formats. 13.6.11 sib subframe 0 control register offset = $080: bit label reset read/write 31-0 sf0aux[31:0] x r/w sf0aux[31:0]: these bits represent the control data to be transmitted during sib subframe 0. this register can be loaded by the cpu asynchronously with respect to the sib frame timing (although special timing restrictions are required whenever an enable/disable command is sent to tc35143 and/or other external codec device). whenever this register is not updated, the previous contents are transmitted during consecutive sib frames. 13.6.12 sib subframe 1 control register offset = $084: bit label reset read/write 31-0 sf1aux[31:0] x r/w sf1aux[31:0]: these bits represent the control data to be transmitted during sib subframe 1. this register can be loaded by the cpu asynchronously with respect to the sib frame timing (although special timing restrictions are required whenever an enable/disable command is sent to tc35143 and/or other external codec device). whenever this register is not updated, the previous contents are transmitted during consecutive sib frames. www.datasheet.in chapter 13 sib module 13-27 13.6.13 sib subframe 0 status register offset = $088: read-only bit label reset read/write 31-0 sf0stat[31:0] ? r sf0stat[31:0]: read-only these bits represent the status data to be read during sib subframe 0. this register can be read by the cpu asynchronously with respect to the sib frame timing. whenever this register is not updated from tc35143 and/or other external codec device, the previous contents are transmitted during consecutive sib frames. 13.6.14 sib subframe 1 status register offset = $08c: read-only bit label reset read/write 31-0 sf1stat[31:0] ? r sf1stat[31:0]: read-only these bits represent the status data to be read during sib subframe 1. this register can be read by the cpu asynchronously with respect to the sib frame timing. whenever this register is not updated from tc35143 and/or other external codec device, the previous contents are transmitted during consecutive sib frames. 13.6.15 sib dma control register offset = $090: bit label reset read/write 31 sndbuff1time 0 r/w 30 snddmaloop 0 r/w 29-18 snddmaptr[13:2] ? r 17 endmarxsnd 0 r/w 16 endmatxsnd 0 r/w 15 telbuff1time 0 r/w 14 teldmaloop 0 r/w 13-2 teldmaloop[13:2] ? r 1 endmarxtel 0 r/w 0 endmatxtel 0 r/w www.datasheet.in chapter 13 sib module 13-28 sndbuff1time: the sound dma controller supports two buffer addressing modes depending on the state of this bit. when sndbuff1time is set to a logic ?1?, the sound dma controller will stop executing when it reaches the end of the dma buffer. when sndbuff1time is cleared to a logic ?0?, the sound dma controller will loop back to the start of the dma buffer when the end of the dma buffer is reached and will continue operating in a continuous and circular manner. snddmaloop: the sound dma controller supports two full-duplex loopback modes depending on the state of this bit. when snddmaloop is set to a logic ?1?, the sound dma controller issues rx dma requests first, followed by tx dma requests. this ordering allows an rx-to-tx immediate loopback via the dma buffer. when snddmaloop is cleared to a logic ?0?, the sound dma controller issues tx dma requests first, followed by rx dma requests. this ordering allows a single circular dma buffer to be used for both tx and rx, if so desired. snddmaptr[13:2]: read-only these bits provide the status of the sound dma counter. endmarxsnd: this bit enables the sound dma receive function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the sndrxstart, sndtxstart, and sibsize registers are setup and the sib module is enabled (ensib asserted) and ensnd is set. either endmarxsnd or endmatxsnd or both can be set at a time since the sound dma controller can support full duplex operation. endmatxsnd: this bit enables the sound dma transmit function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the sndrxstart, sndtxstart, and sibsize registers are setup and the sib module is enabled (ensib asserted) and ensnd is set. either endmarxsnd or endmatxsnd or both can be set at a time since the sound dma controller can support full duplex operation. telbuff1time: the telecom dma controller supports two buffer addressing modes depending on the state of this bit. when telbuff1time is set to a logic ?1?, the telecom dma controller will stop executing when it reaches the end of the dma buffer. when telbuff1time is cleared to a logic ?0?, the telecom dma controller will loop back to the start of the dma buffer when the end of the dma buffer is reached and will continue operating in a continuous and circular manner. teldmaloop: the telecom dma controller supports two full-duplex loopback modes depending on the state of this bit. when teldmaloop is set to a logic ?1?, the telecom dma controller issues rx dma requests first, followed by tx dma requests. this ordering allows an rx-to-tx immediate loopback via the dma buffer. when teldmaloop is cleared to a logic ?0?, the telecom dma controller issues tx dma requests first, followed by rx dma requests. this ordering allows a single circular dma buffer to be used for both tx and rx, if so desired. www.datasheet.in chapter 13 sib module 13-29 teldmaptr[13:2]: read-only these bits provide the status of the telecom dma counter. endmarxtel: this bit enables the telecom dma receive function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the telrxstart, teltxstart, and sibsize registers are setup and the sib module is enabled (ensib asserted) and entel is set. either endmarxtel or endmatxtel or both can be set at a time since the telecom dma controller can support full duplex operation. endmatxtel: this bit enables the telecom dma transmit function. setting this bit to a logic ?1? enables the dma mode. clearing this bit to a logic ?0? disables the dma mode. this bit should not be set until the telrxstart, teltxstart, and sibsize registers are setup and the sib module is enabled (ensib asserted) and entel is set. either endmarxtel or endmatxtel or both can be set at a time since the telecom dma controller can support full duplex operation. www.datasheet.in chapter 13 sib module 13-30 www.datasheet.in chapter 14 spi module 14-1 14. spi module 14.1 overview the spi is a serial interface consisting of clock, data out, and data in. the spi is used to interface to devices such as serial power supplies, serial a/d converters, and other devices that contain simple serial clock and data interfaces. the TMPR3911/12 only supports master mode and generates the spi clock to the slaves. multiple slave devices can share the spi by using a unique chip select for each slave device. the chip select can be generated using one of the general purpose i/o ports on the TMPR3911/12 or tc35143, or using some other output port available in the system. when a device is selected by asserting it?s chip select, the device will shift data in using the spiclk and spiout signals and the device will shift data out using the spiin signal. when a device is not selected then the data output connected to spiin must be tri-stated so other devices can share the spiin signal. the spi module contains registers which provide programmability for spiclk rate, msb first versus lsb first, clock polarity, data phase polarity, and byte mode versus word mode operation. 14.1.1 related pins spiclk: output this pin is used to clock data in and out of the slave device. spiout: output this pin contains the data that is shifted into the slave device. spiin: input this pin contains the data that is shifted out of the slave device. www.datasheet.in chapter 14 spi module 14-2 14.2 description 14.2.1 block diagram spiout baud rate generator data to cpu spiin 16 bit transmitter holding register data from cpu 16 bit shift register 16 bit receiver holding register inter character delay counter interrupt logic figure 14.2.1 spi block diagram the spi module primarily consists of a 16-bit shift register, a 16-bit transmitter holding register, a 16-bit receiver holding register, a baud rate generator, an inter character delay counter, and interrupt logic. a block diagram of the spi module is shown in figure 14.2.1. 14.2.2 baud rate generator the rate of the spiclk signal is determined by the value of the baudrate[3:0] bits in the spi control register. the baudrate[3:0] bits are used by the baud rate generator to divide the spi master clock generated by the clock module logic. the typical frequency of the spi master clock is shown in the table below. table 14.2.1 spi master clock frequency (f spimclk ) main system clock frequency comment tmpr3912au-92/xb-92 9.216 mhz 46.080 mhz f sysclk = 11.520 mhz, rf[1:0] = 00, slowbus = 0 TMPR3911bu/bxb 5.8982 mhz 29.4912 mhz f sysclk = 7.3728 mhz, rf[1:0] = 00, slowbus = 0 www.datasheet.in chapter 14 spi module 14-3 14.2.3 transmitter/receiver the spi module is kept in a reset state until the enspi bit is set in the spi control register. before setting the enspi bit, all other control bits in the spi control register should be set to the desired values. once the enspi bit is set, the spibufavailint interrupt will be asserted to indicate that the spi transmitter holding register is available. the spi logic will then wait until the software writes to the spi transmitter holding register. once the software writes to the transmitter holding register then the contents will be transferred to the shift register and shifted out to the slave device. while data is shifting out to the slave device using the spiout signal, data will shift in using the spiin signal. once the data has finished shifting, the contents of the shift register will be loaded into the receiver holding register and the spircvint interrupt will be asserted to indicate that there is valid receive data in the receiver holding register. once the contents of the transmitter holding register are transferred to the shift register, the spibufavailint interrupt is again asserted to indicate that the transmitter holding register is once again available. therefore the software is supposed to do the following procedure every time it attempts to write data into the transmitter holding register. 1) check if spibufavailint is a logic ?1?. if not, wait for its assertion. 2) clear the spibufavailint status bit. 3) write data into the transmitter holding register. thus, as long as the software can keep the transmitter holding register serviced before the data shifts out of the shift register, the spi can maintain seamless data transfer. if the software fails to keep up with the transfer rate, then the spi will simply wait until the next data is written to the transmitter holding register. at the end of every series of transmission the software is supposed to negate the chip select signal for the target device by the following procedure. 1) check if spibufavailint is a logic ?1?. if not, wait for its assertion. 2) leave the spibufavailint status bit set (do not clear the bit). 3) clear the spiemptyint status bit. 4) wait for spiemptyint assertion. 5) negate the chip select signal. www.datasheet.in chapter 14 spi module 14-4 the spi supports either 8-bit per character or 16-bit per character operation, as defined by the word bit in the spi control register. the software can also select whether the msb or lsb should shift first using the lsb control bit in the spi control register. another set of control bits (clkpol and phapol) select the polarity of the spiclk and determine whether data should be sampled on the rising or falling edge of the spiclk. spi timing is shown in figure 14.2.2. b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 b14 b15 b12 b13 b10 b9 b8 b0 b15 b14 b13 b11 b6 b7 b4 b5 b2 b1 b3 b14 b15 b12 b13 b10 b9 b8 b0 b15 b14 b13 b11 b6 b7 b4 b5 b2 b1 b3 b6 b7 b4 b5 b2 b1 b0 b0 b3 b6 b7 b4 b5 b2 b1 b3 b6 b7 b4 b5 b2 b1 b0 b0 b3 b6 b7 b4 b5 b2 b1 b3 8 bit data transfer non-seamless operation clkpol = 0, phapol = 0, msb first 8 bit data transfer seamless operation clkpol = 0, phapol = 0, msb first 16 bit data transfer seamless operation clkpol = 0, phapol = 0, msb first spiclk spiin spiout spiout spiclk spiin spiclk spiout spiin figure 14.2.2 spi timing 14.2.4 clkpol/phapol the clkpol and phapol bits in the spi control register determine the idle phase of spiclk and the valid clock edge for sampling data. figure 14.2.3 shows the four possible combinations. b6 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 spiclk spiclk spiclk spiclk spiin spiout clkpol = 1 phapol = 0 clkpol = 0 phapol = 1 clkpol = 1 phapol = 1 clkpol = 0 phapol = 0 b7 figure 14.2.3 clkpol/phapol timing www.datasheet.in chapter 14 spi module 14-5 14.2.5 inter character delay counter sometimes it is desirable to guarantee a minimum time between groups of data. the inter character delay counter is used to provide delay between groups of data. if word mode is selected in the spi control register, delay will be inserted after 16 bits of data are shifted. if word mode is not selected, delay will be inserted after 8 bits of data are shifted, as shown in figure 14.2.4. inter character delay is added by setting the delayval[3:0] bits to a value other than $0. the number stored in these bits will directly correspond to the number of spiclk periods of delay that will be inserted between characters. a zero value for these bits will imply seamless operation and the spi will shift data and provide clocks continuously as long as the software keeps up with the transmitter rate. b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 b6 b7 b4 b5 b2 b1 b0 b3 8 bit data transfer seamless operation clkpol = 0, phapol = 0, msb first delayval[3:0] = 2 spiclk spiin spiout figure 14.2.4 inter character delay timing 14.2.6 spi interrupts spibufavailint: this interrupt is set when the enspi bit is first asserted and subsequently when the contents of the spi transmitter holding register are transferred to the spi shift register. this interrupt is used to indicate that the spi transmitter holding register is available to be written by the software. see section 8 for information on how to read and clear interrupts. spierrint: this interrupt is set whenever the spi transmitter holding register is written, but the spibufavailint has not set to indicate that the register is available. this interrupt serves as a overrun indication for the software. see section 8 for information on how to read and clear interrupts. spircvint: this interrupt is whenever the contents of the spi shift register are transferred to the spi receiver holding register. this interrupt is used to indicate that there is valid data in the spi receiver holding register to be read by the software. see section 8 for information on how to read and clear interrupts. spiemptyint: this interrupt is set whenever the both the spi shift register and the spi transmitter holding register are empty. this interrupt can be used by the software to determine when the spi is idle. see section 8 for information on how to read and clear interrupts. www.datasheet.in chapter 14 spi module 14-6 14.3 spi registers 14.3.1 spi control register offset = $160: bit label reset read/write 31-18 reserved 17 spion 0 r 16 empty 1 r 15-12 delayval[3:0] x r/w 11-8 baudrate[3:0] x r/w 7-6 reserved 5 phapol 0 r/w 4 clkpol 0 r/w 3 reserved 2word 0 r/w 1lsb 0 r/w 0enspi 0 r/w spion: read-only when the enspi bit is disabled, the spi will not shut down until the transmitter holding register and shift register are both empty, in order to make sure that any data still in the spi is shifted out. this status bit allows the software to know when the module has shut down as a result of clearing the enspi control bit. empty: read-only this bit is asserted if both the transmitter holding register and shift register are empty and the inter character delay counter is finished inserting delay. this status bit allows the software to know when the spi is idle. delayval[3:0]: these bits define the number spiclk periods of delay to insert between 16-bit or 8-bit characters, depending on whether word mode is selected or not. the value of these bits directly corresponds to the number of spiclk periods of delay. thus, a value of $0 will provide seamless operation with no inter character delay. www.datasheet.in chapter 14 spi module 14-7 baudrate[3:0]: these bits define the rate of the spiclk. these bits divide the spi master clock to generate the desired spiclk rate, as given by the following equation (f spimclk is the frequency of the spi master clock.): spiclk rate = 2 2 0] : baudrate[3 f spimclk + * phapol: setting this bit will cause the transmitter to clock data out on the rising edge of spiclk, to be sampled by the peripherals on the falling edge of spiclk. clkpol: setting this bit will cause the spiclk signal to idle high instead of low. word: setting this bit will cause the spi to shift 16 bits of data in and out. if this bit is cleared, 8 bits of data are shifted. lsb: setting this bit will cause the data to be shifted out to the slave devices and in from the slave devices lsb-first instead of msb-first. enspi: setting this bit will enable the spi module. this bit should only be set after all other control bits have been set to the desired values. when this bit is cleared, the spi will remain active until the shift register and transmitter holding register are both empty. once both registers are empty, the spi will shut down and all the logic will be held in a reset state but gives no effect on the spi control register. 14.3.2 spi transmitter holding register offset = $164: write-only bit label reset read/write 31-16 reserved 15-0 txdata[15:0] x w txdata[15:0]: write-only these bits are the data that is loaded into the transmitter holding register. this register should only be loaded after the spibufavailint interrupt is asserted. if word mode is not set, only bits 7:0 are valid. www.datasheet.in chapter 14 spi module 14-8 14.3.3 spi receiver holding register offset = $164: read-only bit label reset read/write 31-16 reserved 15-0 rxdata[15:0] x r rxdata[15:0]: read-only these bits are the receive data in the receiver holding register. the bits are only valid after the spircvint interrupt is asserted. if word mode is not set, only bits 7:0 are valid. www.datasheet.in chapter 15 timer module 15-1 15. timer module 15.1 overview the timer module consists of two portions. the first is a 40-bit real time clock (rtc) counter that uses a 32.768 khz clock. the counter will provide a maximum count of 388 days. also included is a 40-bit alarm register for the rtc that allows the software to set an alarm at any desired count of the rtc counter. the rtc will generate two interrupts for the cpu. the first is the alarmint that will generate an interrupt whenever the rtc reaches the value set by the alarm. the second is the rtcint that will generate an interrupt whenever the rtc counter ?rolls over? after reaching a count of 388 days. the second portion of the timer module is the periodic timer used by the software to generate periodic interrupts for monitoring system events. the periodic timer uses the timerclk generated by the clock module, which is generated by dividing the clk by 32. the periodic timer contains a programmable 16-bit counter. when enabled, the counter will count down and generate an interrupt (perint) whenever reaching a count of zero. 15.1.1 related pins c32kin: input this pin along with c32kout should be connected to a 32.768 khz crystal. c32kout: output this pin along with c32kin should be connected to a 32.768 khz crystal. bc32k: output this pin is a buffered output of the 32.768 khz clock. www.datasheet.in chapter 15 timer module 15-2 15.2 rtc 15.2.1 rtc block diagram the rtc consists of five 8-bit ripple counters, a 40-bit equality comparator, roll over detect logic and two interrupt flip-flops, as shown in figure 15.2.1. tc3 tc2 = tc1 tc0 tc3 tc4 tc2 tc1 tc0 tc4 8 bit ripple counter rtcint c32k alarmint alarm(39:0) tc tc tc tc tc 8 bit ripple counter 8 bit ripple counter 8 bit ripple counter 8 bit ripple counter figure 15.2.1 rtc block diagram www.datasheet.in chapter 15 timer module 15-3 15.2.2 rtc description the rtc contains five 8-bit ripple counters connected in series. the first counter counts on each c32k clock, while each successive counter only counts when the previous count stage has reached a count of ?$ff?. once all the counters reach a count of ?$ffffffffff?, the rtcint interrupt will assert to indicate that the counter is ?rolling over?. given a 40-bit counter for the rtc and an input clock c32k of 32.768 khz, the time until the rtcint interrupt will assert is 388 days. the software can generate an alarm interrupt (alarmint) by setting the alarm[39:0] bits in the alarm register. whenever the rtc becomes equal to the value set in the alarm register, the alarmint will be triggered. the value of the rtc counter can be read via the rtc register. the rtc counter is split into groups of five 8-bit counters to simplify ic testing. 15.2.3 rtc interrupts rtcint: this interrupt is set whenever all 40 bits of the rtc counter reach a value of ?$ffffffffff? to alert the software that the counter is ?rolling over?. see section 8 for information on how to read and clear interrupts. alarmint: this interrupt is set whenever the rtc counter reaches a count that is equal to the value of the alarm[39:0] bits set in the alarm register. see section 8 for information on how to read and clear interrupts. www.datasheet.in chapter 15 timer module 15-4 15.3 periodic timer 15.3.1 periodic timer block diagram the periodic timer consists of a 16-bit down counter, along with a zero detect and an interrupt flip- flop, as shown in figure 15.3.1. timerclk perval[15:0] perint ld 16-bit down counter = 0 figure 15.3.1 periodic timer block diagram 15.3.2 periodic timer description the periodic timer is used by the software to generate periodic interrupts needed to monitor system events. the periodic timer contains a 16-bit down counter whose initial value is programmed by the software via the perval[15:0] control bits in the periodic timer register. the counter uses the timerclk signal generated by the clock module as the clock for the counter. with a system clock of 36.864 mhz, the timerclk will normally be set to 1.152 mhz. this implies a maximum periodic timer count duration of 56.89 ms with a granularity of 0.87 s. the periodic timer is enabled by asserting the enpertimer control bit in the timer control register. once enabled, the counter will load the perval[15:0] control bits and down count to zero. once the count of zero is reached, the perint interrupt is asserted and the counter re-loads the perval[15:0] control bits. the value of the periodic timer counter can be read by the software via the percnt[15:0] status bits in the periodic timer register. 15.3.3 periodic timer interrupts perint: this interrupt is set whenever the periodic timer is enabled and the periodic timer counter reaches a count of zero. see section 8 for information on how to read and clear interrupts. www.datasheet.in chapter 15 timer module 15-5 15.4 timer registers 15.4.1 rtc register offset = $140: read-only bit label reset read/write 31-8 reserved 7-0 rtc[39:32] x r offset = $144: read-only bit label reset read/write 31-0 rtc[31:0] x r rtc[39:0]: read-only these bits provide the status of the 40-bit rtc counter. the software must read these bits twice and compare the values to ensure that the counter is not read while the counter is counting since the cpu clock is not synchronous with the rtc counter clock. if the result of the comparison is not equal, the software must read the register again to read the correct count value. 15.4.2 alarm register offset = $148: bit label reset read/write 31-8 reserved 7-0 ararm[39:32] x r/w offset = $14c: bit label reset read/write 31-0 ararm[31:0] x r/w alarm[39:0]: whenever the rtc counter reaches a count that is equal to these bits, the alarmint interrupt will be set. www.datasheet.in chapter 15 timer module 15-6 15.4.3 timer control register offset = $150: bit label reset read/write 31-8 reserved 7freezepre 0 r/w 6freezertc 0 r/w 5 freezetimer 0 r/w 4 enpertimer 0 r/w 3 rtcclr 0 r/w 2testc8ms 0 r/w 1entestclk 0 r/w 0 enrtctst 0 r/w freezepre: setting this bit will cause the lower 8 bits of the rtc counter to freeze. the lower 8 bits of the rtc counter are also used to generate an 8 ms reference signal for the ir carrier detect state machine and the debouncers in the power module and i/o module. thus, setting this bit will also cause these modules to lose their 8 ms reference signal. this bit can be used by the software to freeze the rtc counter during software debugging. freezertc: setting this bit will cause the upper 32 bits of the rtc counter to freeze. this bit can be used by the software to freeze the rtc counter during software debugging. freezetimer: setting this bit will cause the periodic timer counter to freeze. this bit can be used by the software to freeze the periodic timer counter during software debugging. enpertimer: setting this bit will cause the periodic timer to load the perval[15:0] control bits and begin down counting. the perint interrupt will only be asserted if this bit is enabled. rtcclr: setting this bit to a logic ?1? will cause all 40 bits of the rtc counter to initialize to ?$0000000000?. the rtc counter will stay cleared and the counter will not start counting until this bit is cleared back to a logic ?0?. www.datasheet.in chapter 15 timer module 15-7 testc8ms: setting this bit will cause the 8 ms reference pulse used by the ir logic and the debouncer circuits to run at 61 s instead of 8 ms. this bit is used for ic testing to speed up the counters and should normally never be set by the software. entestclk: setting this bit will cause the 32 khz input clock for the rtc counter to be driven by the timerclk instead of the 32 khz input pin. this bit is used for ic testing to speed up the amount of time needed to test the rtc counter and should normally never be set by the software. enrtctst: setting this bit will cause all five of the 8-bit counters that comprise the rtc counter to count together. this provides a mechanism for fully exercising all the counters in a timely fashion for ic testing. the software may wish to set this bit in order to test the rtcint interrupt since normally it would take 388 days to generate this interrupt. 15.4.4 periodic timer register offset = $154: bit label reset read/write 31-16 percnt[15:0] x r 15-0 perval[15:0] x r/w percnt[15:0]: read-only these bits provide the status of the periodic counter. the software should continually read this register until two consecutive reads provide the same value, in order to ensure that the register is not read while the counter is counting, since the timerclk is not synchronous with the cpu clock. perval[15:0]: these bits are loaded into the periodic timer counter when the counter is enabled or when the counter reaches a count of zero. the perint time is expressed by the following formula (f timerclk is the frequency of the timerclk). interrupt rate = timerclk f 1 0] : perval[15 + www.datasheet.in chapter 15 timer module 15-8 www.datasheet.in chapter 16 uart module 16-1 16. uart module 16.1 overview the uart module contains two identical, fully independent, full duplex uarts: uarta and uartb. each uart contains the following features: ? adjustable baud rate counter from 230 khz down to 225 hz ? single buffered transmit register ? double buffered receive register ? dma for either transmit or receive ? full duplex ? even, odd or no parity ? 7 or 8 bits per character ? one or two stop bits per character ? pulse option mode to support irda infrared protocol 16.1.1 related pins txd: output this pin is the uart transmit signal from the uarta module. rxd: input this pin is the uart receive signal to the uarta module. irout: output this pin is the uart transmit signal from the uartb module or the consumer ir output signal if consumer ir mode is enabled. irin: input this pin is the uart receive signal to the uartb module. www.datasheet.in chapter 16 uart module 16-2 16.2 overall operation the operation of each uart is controlled through six registers: control 1 register, control 2 register, dma control 1 register, dma control 2 register, dma count register, and transmit/receive holding register. 16.2.1 power on/off each uart is powered on and off with the enuart bit of the control 1 register. when the enuart bit is cleared, the uart will power off only after all data in its transmit shift and holding registers has been clocked out. the on/off status of the uart can be monitored via the uarton bit of the control 1 register. while powered off, the uart is completely disabled. in addition to being powered on, each uart must also have its clock enabled to operate. the uart clock enables, as well as the uart clock frequency, is controlled by the clock module (see section 6). 16.2.2 baud rate and communication parameters the baud rate, bits per symbol (7 or 8), parity type (none, even, or odd), and line polarity (normal or inverted) apply to both the transmitter and receiver and may not be independently selected for each direction. all of these except the baud rate are selected with individual bits of the control 1 register (see register descriptions in section 16.5). the baud rate for each uart is determined by the baudrate value in the control 2 register and the uart clock frequency (f uartclk ). the following equation determines the baud rate: baud rate = f uartclk ((baudrate + 1) * 16) the uart clock frequency is determined by the clock module configuration (see section 6). table 16.2.1 shows the value that should be written to the baudrate control bits to generate the standard baud rates. table 16.2.1 standard uart baud rates baud rate baudrate (when f uartclk = 1.8432 mhz) baudrate (when f uartclk = 3.6864 mhz) baudrate (when f uartclk = 9.216 mhz) 115200 0 1 4 57600 1 2 9 38400 2 5 14 19200 5 11 29 9600 11 23 59 4800 23 47 119 2400 47 95 239 1200 95 191 479 600 191 383 959 300 383 767 1919 www.datasheet.in chapter 16 uart module 16-3 16.2.3 interrupt operation each uart may be configured to generate cpu interrupts for a number of events. when any of these events occur, a corresponding status bit will be set in the interrupt status 2 register (see section 8 for details on the interrupt module). table 16.2.2 lists the uart events that can generate interrupts. the entries are in terms of the mnemonic used in this document and the actual event. in the mnemonic the lower-case ?n? is replaced with ?a? for uarta or ?b? for uartb. table 16.2.2 uart interrupt events mnemonic interrupting event uartnrxint receiver holding register becomes full uartnrxoverrunint receiver shift register becomes full when both holding register and prxhold are full uartnframeerrint receiver does not detect stop bit-character not 0x0 uartnbreakint receiver detects break condition-character is 0x0 and no stop bit uartnparityerrint receiver detects parity bit error uartntxint transmit holding register becomes empty uartntxoverrunint transmit holding register written to when full uartnemptyint transmit shift register becomes empty when holding register is also empty uartndmafullint dma controller reaches end of specified buffer uartndmahalfint dma controller reaches half-way point in specified buffer while these events cause a bit to be set in interrupt status 2 register, they will not cause an interrupt unless they are configured to do so. interrupts are enabled through the enable interrupt 2 register. interrupt status bits are cleared through the clear interrupt 2 register. note that interrupt status bits are set and need to be cleared regardless of whether or not the interrupt is enabled. see section 8 for more general information about the TMPR3911/12 interrupts. 16.2.3.1 responding to interrupt status bits when responding to an event (whether via interrupt or polling), it is important to clear the interrupt status bit before taking the action that will re-enable the event. this will ensure that an event will not be missed. for example, when the receive holding register becomes full, the uartnrxint bit will get set. if the receive holding register is read before the uartnrxint bit is cleared, it is possible that sometime after the receive holding register becomes empty and before the uartnrxint bit is cleared, a second character will be transferred to the receive holding register. this transfer will also cause the uartnrxint bit to be set. obviously, if the cpu (still reacting to the first event) then clears the uartnrxint bit, the second event will be missed. as a result, the cpu will not be ?aware? that the receive holding register is full and an overrun interrupt will eventually occur. www.datasheet.in chapter 16 uart module 16-4 16.2.3.2 related interrupts uartarxint: issues an interrupt whenever the uarta receive holding register is loaded with data. uartarxoverrunint: issues an interrupt if the uarta receive holding register is loaded twice before the interrupt is service. uartaframeerrint: issues an interrupt if the current data in the uarta receive holding register contains a frame error. uartabreakint: issues an interrupt if the current data in the uarta receive holding register is a break. uartaparityerrint: issues an interrupt if the current data in the uarta receive holding register contains a parity error. uartatxint: issues an interrupt if the uarta transmit holding register is available. uartatxoverrunint: issues an interrupt if the uarta transmit holding register is written to when the transmit holding register is not available. uartaemptyint: issues an interrupt if the uarta transmit holding register and transmit shift register are both empty. uartadmafullint: issues an interrupt if the uarta dma counter reaches the end of the buffer. uartadmahalfint: issues an interrupt if the uarta dma counter reaches the mid point of the buffer. uartbrxint: issues an interrupt whenever the uartb receive holding register is loaded with data. uartbrxoverrunint: issues an interrupt if the uartb receive holding register is loaded twice before the interrupt is service. www.datasheet.in chapter 16 uart module 16-5 uartbframeerrint: issues an interrupt if the current data in the uartb receive holding register contains a frame error. uartbbreakint: issues an interrupt if the current data in the uartb receive holding register is a break. uartbparityerrint: issues an interrupt if the current data in the uartb receive holding register contains a parity error. uartbtxint: issues an interrupt if the uartb transmit holding register is available. uartbtxoverrunint: issues an interrupt if the uartb transmit holding register is written to when the transmit holding register is not available. uartbemptyint: issues an interrupt if the uartb transmit holding register and transmit shift register are both empty. uartbdmafullint: issues an interrupt if the uartb dma counter reaches the end of the buffer. uartbdmahalfint: issues an interrupt if the uartb dma counter reaches the mid point of the buffer. 16.2.4 dma operation each uart has one dma channel which may be used with either the transmitter or the receiver. dma operation involves specifying a memory buffer and enabling dma. once enabled, characters will flow either from the memory buffer to the transmitter, or from the receiver to the memory buffer. the memory buffer is specified in terms of its start address in physical address space, and its length in bytes. note that the cpu must know the mapping between virtual and physical addresses. the start address must be written to the dma control 1 register. the two lsbs are ignored, thereby forcing the buffer to begin on a long word boundary. the buffer length minus one must be written to the dma control 2 register. once the buffer has been specified, dma may be enabled. this is done with either endmarx or endmatx in the control 1 register. only one of these two bits should be set at any one time. operation is undefined if both are set. once enabled, uart dma will begin. for the transmitter, this means that when the transmit holding register becomes empty, the dma controller will transfer a byte from the specified buffer to the transmit holding register, and update its internal buffer pointer. for the receiver, this means that when the receive holding register becomes full, the dma controller will transfer a byte from the receive holding register to the specified buffer, and update its internal buffer pointer. www.datasheet.in chapter 16 uart module 16-6 the endmaloop control bit in the control 1 register determines when dma will stop. if this bit is cleared, dma will stop when the end of the buffer is reached. if this bit is set, the dma controller will run continuously, looping back to the start of the buffer when the buffer end is reached. in either case, dma can be explicitly halted by clearing the endmarx or endmatx bit. the dma count register is a read-only register which contains the uart dma controller?s buffer counter status. the counter counts up so that the value in this status register indicates how much of the buffer remains to be accessed (on this pass) by the dma controller. there are two interrupt status bits associated with the dma controller: uartndmafullint and uartndmahalfint. these are set as the dma controller buffer pointer reaches the end and the half-way point of the buffer. half-buffer interrupt end-of-buffer interrupt dma addr byte enable dma count 16 16 16 24 30 30 one-time vs. circular mode control from cpu dma startval cntl reg uart cntl 1 reg dma length cntl reg 2 cnt load logic addr cnt cmp cmp byte enable gen figure 16.2.1 uart dma 16.2.5 internal loopback the loopback bit of the control 1 register, when set, places the uart in an internal loopback mode. when in this mode, the transmit and receive lines of the uart are internally tied together, the external transmit line is driven high, and the external receive line is ignored. this loopback mode is for testing purposes only. www.datasheet.in chapter 16 uart module 16-7 16.3 transmitter operation figure 16.3.1 shows a block diagram of the transmitter portion of each uart. characters to be transmitted are written by the cpu to the transmit holding register. this should only be done when the transmit holding register is empty which is indicated by either the empty bit of the control 1 register, or the uartntxint interrupt. writing a character to the transmit holding register when it is not empty results in a transmitter overrun. the character in the transmit holding register is transferred into the transmit shift register when the transmit shift register becomes empty. transferred with the character is 1 start bit, 1 or 2 stop bits (depending on the setting of twostop in the control 1 register), and 0 or 1 parity bits (depending on the setting of enparity and evenparity in the control 1 register). beginning at the next baud period following the transfer, the character is shifted out to the transmit line. the start bit is shifted first, followed by the lsb through msb of the (7-bit or 8-bit) character, followed by the parity bit (if any), and ending with the stop bit(s). as the last stop bit is shifted out, the transmitter will load the next character from the transmit holding register if one has been written. if the transmit holding register is empty, the transmit shift register will continue to shift out stop bits (logic level ?1?) until a character is written by the cpu into the transmit holding register. depending on the configuration, as few as nine bits (7-bit characters, no parity, 1 stop bit), and as many as twelve bits (8-bit characters, parity enabled, 2 stop bits) are transmitted for every character. transmit holding register transmit shift register uarttxd (internal to receiver) loopback dtinvert distxd pulseopt1 pulseopt2 pulse option generator 2:1 mux 16 evenparity txdata[7:0] break twostop bit_7 enparity 10-bit counter baudrate[9:0] uart master clock parity generator figure 16.3.1 uart transmitter www.datasheet.in chapter 16 uart module 16-8 16.3.1 transmitter pulse output operation in normal operation (neither pulse option selected), the transmit line is tied directly to the transmit shift register output. each transmitted bit causes the transmit line to go high or low for a full baud period. to support the irda infrared protocol, there are two pulse options which result in a modified signal on the output line. when either of these options are selected, transmitted zeros will cause the transmit line to go low for only a fraction of the baud period. ones are transmitted normally. the difference between the two pulse option modes is the duration that the line will stay low for each transmitted zero. pulse option 1 (selected with pulseopt1 of the control 1 register) results in a duration of six uart clock cycles. the uart clock frequency is controlled by the clock module (see section 6), when the uart clock frequency is 3.6864 mhz, the low pulse is 1.63 s ( = 6 3.6864). note that this duration is irrespective of the baud rate. pulse option 2 (selected with pulseopt2 of the control 1 register) results in a duration of 3/16 of the selected baud period. the mode of operation with both pulse options selected (both pulseopt1 and pulseopt2 asserted) is reserved for a future implementation. 16.3.2 transmitter disable operation the transmit line may be disabled with the distxd bit of the control 1 register. in this mode the transmit line is held at logic level ?0?. otherwise, the transmitter operates normally as described above. 16.3.3 transmitter break operation a break may be transmitted by writing the value 0x100 to the transmit holding register. the break is transmitted after the character (if any) in the transmit shift register is sent. the break condition continues until explicitly terminated by the cpu. the cpu may continue to write the value 0x100 to the transmit holding register in order to control the duration of the break precisely. the break condition is terminated when the cpu writes the value 0x00 to the transmit holding register. 16.3.4 transmitter overrun the transmit overrun condition occurs if the cpu writes a character to the transmit holding register when it is not empty. this condition is indicated by the uartntxoverrunint interrupt status bit. the character in the transmit holding register resulting from an overrun is undefined. www.datasheet.in chapter 16 uart module 16-9 16.4 receiver operation figure 16.4.1 shows a block diagram of the receiver portion of each uart. in normal operation, the receiver waits for a start bit on the receive line. one baud cycle after receiving the start bit, the next 7 or 8 bits (depending on bit_7 in the control 1 register) are clocked into the receive shift register. if parity is enabled (depending on enparity and evenparity in the control 1 register), the next bit is compared with the expected parity. as the stop bit is clocked in and checked, the assembled character is transferred from the receive shift register to the prxhold register. the prxhold register is a buffer between the receive shift register and the receive holding register. the prxholdfull bit of the control 1 register, when asserted, indicates that the prxhold register is full. on the first uart clock period that the receive holding register is empty and the prxhold register is full, the character is transferred to the receive holding register. this transfer results in the rxholdfull bit of the control 1 register and the uartnrxint interrupt status bit both asserting. 2:1 mux rxdata[7:0] receive shift register receive buffer register prxho ld receive holding register receive logic: sync, parity & break control bit_7 enparity evenparity enbreakhalt dtinvert loopback pulseopt2 pulseopt1 uartrxd baudrate[9:0] uart master clock (internal from transmitter) pulse option decoder 10-bit counter figure 16.4.1 uart receiver www.datasheet.in chapter 16 uart module 16-10 16.4.1 receiver break operation the receiver detects a break condition when the received character is 0x00 and there is no stop bit. when this occurs the receiver generates a uartnbreakint interrupt. the interrupt does not assert until the break character is transferred to the receive holding register. in other words, the interrupt is held off until all characters preceding the break are read by the cpu. additionally, the operation of the receiver in response to a break is affected by the enbreakhalt bit of the control 1 register. normally (with the enbreakhalt bit cleared), the receiver will start receiving characters again as soon as a stop bit is detected on the line. however, if the enbreakhalt bit is set, the receiver shuts down until the break character is read by the cpu from the receive holding register. while shut down, the receiver ignores all data on the receive line. 16.4.2 receiver frame error condition a receiver frame error occurs when the receiver does not detect a stop bit following the character. this condition results in a uartnframeerrint interrupt being generated. like the uartnbreakint interrupt, the interrupt is not asserted until the character associated with the frame error is transferred to the receive holding register. 16.4.3 receiver overrun condition a receiver overrun occurs when a character is received and both the prxhold register and receive holding register are full. this condition occurs at the point that the stop bit of the new character is clocked in and results in a uartnrxoverrunint interrupt. the new character will overwrite the character in the prxhold register. like the uartnbreakint interrupt, the interrupt is not asserted until the character associated with the overrun error is transferred to the receive holding register. 16.4.4 receiver parity error condition a receiver parity error occurs when parity is enabled and the receiver detects the wrong polarity of the bit following the character and preceding the stop bit. this condition results in a uartnparityerrint interrupt being generated. like the uartnbreakint interrupt, the interrupt is not asserted until the character associated with the parity error is transferred to the receive holding register. 16.4.5 receiver pulse operation in normal operation the received signal corresponds to the polarity of the data for the entire baud period. when the received signal is from a pulsed transmitter, zeros are low for only a fraction of the baud period. if either pulse option is selected (with pulseopt1 or pulseopt2 of the control 1 register) the receiver reconstructs the data stream by extending low pulses to the full baud period. www.datasheet.in chapter 16 uart module 16-11 16.5 uart registers 16.5.1 uart control 1 register offset = $0b0: uarta offset = $0c8: uartb bit label reset read/write 31 uarton 0 r 30 empty 1 r 29 prxholdfull 0 r 28 rxholdfull 0 r 27-16 reserved 15 endmarx 0 r/w 14 endmatx 0 r/w 13 testmode 0 r/w 12 enbreakhalt 0 r/w 11 endmatest 0 r/w 10 endmaloop 0 r/w 9pulseopt2 0 r/w 8pulseopt1 0 r/w 7 dtinvert 0 r/w 6distxd 1 r/w 5twostop 0 r/w 4 loopback 0 r/w 3bit_7 0 r/w 2 evenparity 0 r/w 1 enparity 0 r/w 0 enuart 0 r/w uarton: read-only when the enuart bit is disabled, the module will not shut down until the transmit holding register and transmit shift register are empty plus a couple of clocks. this bit provides the status as to whether the module is still enabled or not. www.datasheet.in chapter 16 uart module 16-12 empty: read-only this bit is high if the transmit holding register and transmit shift register are both empty. prxholdfull: read-only the receive data path consists of an 8-bit shift register plus two 8-bit holding registers. whenever the receiver finishes receiving a character, it will transfer the contents into the prxhold register. the contents of this register will then be loaded into the rxhold register whenever this rxhold register is empty. the rxhold register is emptied by reading a byte from the receive holding register. this prxholdfull bit provides status as to whether there is a valid byte of data in the prxhold register. rxholdfull: read-only this bit provides the status of the rxhold register. endmarx: this bit enables the dma receive function. this bit should not be set until the uartdmacntl1 and uartdmacntl2 registers are setup and the module is enabled. only one of endmarx or endmatx can be set at a time since there is only one dma channel. endmatx: this bit enables the dma transmit function. this bit should not be set until the uartdmacntl1 and uartdmacntl2 registers are setup, the module is enabled and the empty flag is set. only one of endmarx or endmatx can be set at a time since there is only one dma channel. testmode: this bit is used for ic testing and should never be set. enbreakhalt: setting this bit will cause the receiver to halt after receiving a break, until the receive holding register is emptied and the uartrxd signal goes to the marking state. otherwise, the receiver will halt until the uartrxd signal goes to the marking state without regard to the status of the receive holding register. endmatest: this bit is used for ic testing and should not be set. endmaloop: the dma controller supports two modes depending on the state of this bit. when endmaloop is low, the dma controller will stop executing when it reaches the end of the dma buffer. when endmaloop is high, the dma controller will loop back to the start of the dma buffer when the end of the dma buffer is reached and will continue operating. pulseopt2: setting this bit will cause the transmitted data to pulse low for three baud clocks instead of the normal 16 baud clocks. setting either this bit or pulseopt1 will cause the receiver to expect the data to be a pulsed input. www.datasheet.in chapter 16 uart module 16-13 pulseopt1: setting this bit will cause the transmitted data to pulse low for a fixed six uart clocks instead of the normal 16 baud clocks. dtinvert: setting this bit will cause the uarttxd and uartrxd signals to be inverted. distxd: setting this bit will cause the uarttxd signal to go low. twostop: setting this bit will cause the transmitter to transmit two stop bits instead of the normal one stop bit. loopback: setting this bit will cause the transmitted data to internally loop back to the receive data. the uarttxd pin is held high when this bit is set. bit_7: setting this bit selects 7-bit per character mode instead of 8-bit per character mode. evenparity: setting this bit selects even parity instead of odd parity, if the enparity bit is set. enparity: setting this bit will cause parity to be generated and received. enuart: setting this bit will enable the uart module. when this bit is cleared the module is kept in a reset state but clearing this bit gives no effect on the uart control 1 register. this bit should not be set until all other control bits are setup. www.datasheet.in chapter 16 uart module 16-14 16.5.2 uart control 2 register offset = $0b4: uarta write-only offset = $0cc: uartb write-only <TMPR3911bu, TMPR3911bxb> bit label reset read/write 31-10 reserved 9-0 baudrate[9:0] x w chapter 16 uart module 16-15 16.5.5 uart dma count offset = $0c0: uarta read-only offset = $0d8: uartb read-only bit label reset read/write 31-16 reserved 15-0 dmacnt[15:0] x r dmacnt[15:0]: read-only these bits provide the status of the dma counter. 16.5.6 uart transmit holding register offset = $0c4: uarta write-only offset = $0dc: uartb write-only bit label reset read/write 31-9 reserved 8break x w 7-0 txdata[7:0] x w break: write-only setting this bit, along with writing $00 to txdata[7:0], will cause a break to be generated. the break will continue until this bit is cleared, along with txdata[7:0] maintained at $00. this register should only be loaded after the uarttxint interrupt is set. the break will flow through the transmit holding register, thus it will not start the break until the current character that is being transmitted from the transmit shift register is finished. txdata[7:0]: write-only these bits are the data to be transmitted. this register should only be loaded after the uarttxint interrupt is set. for 7-bit mode, only bits 6:0 are valid. 16.5.7 uart receiver holding register offset = $0c4: uarta read-only offset = $0dc: uartb read-only bit label reset read/write 31-8 reserved 7-0 rxdata[7:0] x r rxdata[7:0]: read-only these bits are the receive data. the bits are valid after the uartrxint interrupt is set or when the rxhold flag is asserted. for 7-bit mode, only bits 6:0 are valid. www.datasheet.in chapter 16 uart module 16-16 www.datasheet.in chapter 17 video module 17-1 17. video module 17.1 overview the video module within the TMPR3911/12 contains logic for transferring bit-mapped graphics data between a video buffer located in system memory to an external lcd. the lcd must be refreshed at a rate of 50 to 100 frames per second to maintain a steady picture on the display. data is clocked into the lcd?s shift register using parallel data lines (4 or 8 bits wide). once a horizontal line of data has been shifted into the shift register, this line of pixels is transferred to successive lines of the lcd panel. this sequence is repeated until all the lines of the display have been shifted and transferred, producing a full frame of display. at the end of the frame the pointers in the lcd return to the top of the display. different lcd?s have different requirements on the number of horizontal and vertical pixels, the number of parallel lines required for the data interface, interface timing, and refresh rate. the video module inside the TMPR3911/12 is programmable in order to support many different types of lcd?s. the video module also contains logic that produces 4-level or 16-level gray scale on a monochrome lcd using a time-based dithering algorithm. also supported is an 8-bit per pixel color mode for interfacing to color lcd?s. 17.1.1 related pins frame: output this pin is the frame synchronization pulse signal between the video module and the lcd, and is used by the lcd to return its pointers to the top of the display. the video module asserts frame after all the lines of the lcd have been shifted and transferred, producing a full frame of display. df: output this pin is the ac signal for the lcd. since lcd plasma tends to deteriorate whenever subjected to a dc voltage, the df signal is used by the lcd to alternate the polarity of the row and column voltages used to turn the pixels on and off. the df signal can be configured to toggle on every frame or can be configured to toggle every programmable number of load signals. load: output this pin is the line synchronization pulse signal between the video module and the lcd, and is used by the lcd to transfer the contents of it?s horizontal line shift register to the lcd panel for display. the video module asserts load after an entire horizontal line of data has been shifted into the lcd. cp: output this pin is the clock signal for the lcd. data is pushed by the video module on the rising edge of cp and sampled by the lcd on the falling edge of cp. vdat[3:0]: output these pins are the data for the lcd. these signals are directly connected to the lcd for 4-bit non-split displays. for 4-bit split and 8-bit non-split displays, an external register is required to demultiplex the 4-bit data into the desired 8 parallel data lines needed for the lcd. www.datasheet.in chapter 17 video module 17-2 dispon: output this pin is the display-on enable signal for the lcd. viddone: output this pin is used to externally synchronize events to periods when the video is not shifting. 17.2 interface requirements 17.2.1 display types the video module interface supports 3 types of lcd?s: 4-bit split, 4-bit non-split, and 8-bit non split. figure 17.2.1 shows these 3 different display types for monochrome displays and figure 17.2.2 shows these 3 different display types for color displays. a 4-bit split display uses 8 parallel data lines to shift data to both the upper and lower halves of the display simultaneously, with four bits of data shifted to the upper half and four bits of data shifted to the lower half. the end of frame is reached when each half of the display has been shifted and transferred. the video module within the TMPR3911/12 contains control logic which generates the appropriate video buffer addressing required for split displays (see section 17.3.5). since the TMPR3911/12 only provides 4 pins for video output data (vdat[3:0]), an external 4-bit register is required to demultiplex the 4-bit data into the desired 8 parallel data lines (4 upper, 4 lower) needed for the lcd, as shown in figure 17.2.4. a 4-bit non-split display uses 4 parallel data lines to shift data to successive single horizontal lines of the display at a time, until the entire frame has been shifted and transferred. no external register is required for this configuration; the 4 pins for video output data from the TMPR3911/12 can be directly connected to the lcd. an 8-bit non-split display uses 8 parallel data lines to shift data to successive single horizontal lines of the display at a time, until the entire frame has been shifted and transferred. this operates the same as the 4-bit non-split display, except that 8 parallel lines are shifted at a time instead of 4 parallel lines. as also required for the 4-bit split displays, an external 4-bit register is required to demultiplex the 4-bit video output data from the TMPR3911/12 into the desired 8 parallel data lines needed for the 8-bit non- split lcd, as shown in figure 17.2.4. monochrome displays require 1 bit of video data per pixel. figure 17.2.1 shows the pixel ordering of the parallel data lines for the 3 types of monochrome displays. color displays require 3 bits (red, green, and blue) of video data per pixel, resulting in a horizontal shift register of length 3 times the number of pixels per horizontal line. this rgb-tri is shifted to the lcd as consecutive bits via the parallel data lines. figure 17.2.2 shows the rgb-tri and pixel ordering of the parallel data lines for the 3 types of color displays. www.datasheet.in chapter 17 video module 17-3 ud3 ud2 ud1 ud0 ld3 ld2 ld1 ld0 ud3 ud2 ud1 ud0 ud3 ud2 ud1 ud0 ld3 ld2 ld1 ld0 8-bit non-split display 4-bit split display 4-bit non-split display figure 17.2.1 monochrome display types www.datasheet.in chapter 17 video module 17-4 4-bit split display ud3 r1 one pixel 8-bit non-split display 4-bit non-split display ud2 g1 ud1 b1 ud0 r2 ud3 g2 ud2 b2 ud1 r3 ud0 g3 ud3 b3 ud3 r1 ud2 g1 ud1 b1 ud0 r2 ud3 g2 ud2 b2 ud1 r3 ud0 g3 ud3 b3 one pixel ud3 r1 ud2 g1 ud1 b1 ud0 r2 ud3 g2 ud2 b2 ud1 r3 ud0 g3 ud3 b3 one pixel ud3 r1 ud2 g1 ud1 b1 ud0 r2 ud3 g2 ud2 b2 ud1 r3 ud0 g3 ud3 b3 figure 17.2.2 color display types www.datasheet.in chapter 17 video module 17-5 17.2.2 timing requirements data is shifted from the TMPR3911/12 to the lcd using the vdat[3:0] signals. the cp signal is used to clock the data into the lcd?s shift register. after each horizontal line of data has been shifted into the lcd?s shift register, the load signal is asserted to cause the line to be displayed on the lcd panel. then after all of the lines have been displayed, the frame signal is asserted to cause the lcd?s line pointer to start over at the top of the display. figure 17.2.3 shows the various timing requirements for the lcd interface (the example shown is for 4-bit non-split displays). the df signal provides an ac reference for the display. since lcd plasma tends to deteriorate whenever subjected to a dc voltage, the df signal is used by the lcd to alternate the polarity of the row and column voltages used to turn the pixels on and off. the df signal can be configured to toggle on every frame (dfmode = 0) or can be configured to toggle every programmable number of load signals (dfmode = 1), with this toggle period determined by the dfval[7:0] control register setting. figure 17.2.3 shows an example for dfmode = 0 and for dfmode = 1 with dfval[7:0] = $1. the rate of the cp clock signal is controlled by the baudval[4:0] control register setting. the number of cp clock pulses per line busted between successive load pulses is determined by the number of pixels per line programmed into the horzval[8:0] control register. the vidrate[9:0] control register setting determines the frequency of the load pulses, which corresponds to the video line rate. this line rate, along with the number of lcd lines programmed into the lineval[9:0] control register, then determines the video frame rate. www.datasheet.in chapter 17 video module 17-6 load df full frame timing, dfmode = 1, dfval[7:0] = $1 line 1 line 4 line 3 line 2 line 1 frame clock and data timing line 1 shifted during this time 1st line timing expanded view full frame timing, dfmode = 0 load df frame cp load df frame vdat[3:0] cp load df frame line 1 line n line n-1 line 4 line 3 line 2 line 1 line n line n-1 expanded view figure 17.2.3 lcd timing www.datasheet.in chapter 17 video module 17-7 as mentioned previously, since the TMPR3911/12 only provides 4 pins for video output data (vdat[3:0]), an external 4-bit register is required to demultiplex the 4-bit data into the desired 8 parallel data lines needed for both 4-bit split and 8-bit non-split lcd?s, as shown in figure 17.2.4. to support these configurations, the video module drives the vdat output data in a time-multiplexed format, alternating 4 bits of upper data (ud) with 4 bits of lower data (ld) on successive data cycles. the ud data is latched using the external register with cp used as the register?s clock. then, the lcd can clock in all 8 bits in parallel (ud plus ld, which are the vdat signals directly connected to the lcd) using the falling edge of cp, as shown in figure 17.2.5. 4 4 TMPR3911/12 cp ud(3:0) ld(3:0) 4b reg cp lcd vdat[3:0] 4 figure 17.2.4 external register configuration for 4-bit split and 8-bit non-split displays ud ud ud ud ud ud ud ld ud ld ud ld ud ld ud ld ud ld load latched with external register frame clock and data timing, 4-bit split or 8-bit non-split displays ud[3:0] vdat[3:0] cp df figure 17.2.5 lcd timing for 4-bit split and 8-bit non-split displays www.datasheet.in chapter 17 video module 17-8 17.3 implementation 17.3.1 block diagram dither selector 28 4 32 video dma request control video halt/freeze control cp, load, df, frame 2-bit gray data 4-bit gray data 8-bit color data dither patterns mode select: mono vs. gray/color 8-bit color lut data from dma video dma addr horizontal counter video state machine 4-bit vs. 8-bit mode splt vs. non-split mode vdat 2:1 mux mode select: 2-bit gray vs. 4-bit gray vs. 8-bit color 1-bit mono data 3:1 mux 4 ? 32 mux array bluesel[15:0] greensel[31:0] redsel[31:0] 2-bit gray scale lut fifolo fifohi fifob fifoa vidbank[31:20] vidbaselo[19:4] vidbasehi[19:4] vidrate[9:0] baudval[4:0] dfval [ 7:0 ] lineval[8:0] horzval[8:0] line counter dma addr gen dithering frame counters dithering line counters figure 17.3.1 video module block diagram www.datasheet.in chapter 17 video module 17-9 17.3.2 video state machine the video state machine contains programmable logic which allows the TMPR3911/12 to support the different interface timing and rates commonly found in different lcd?s. this is implemented using several sets of programmable counters. the cp clock rate is controlled by the baud rate counter, which is preloaded with the baudval[4:0] control register setting. this counter generates the baud clock by dividing down from the main video clock (which is the same rate as clk). the baud rate counter is free-running, except whenever the halt or freezeframe conditions are asserted. the halt condition occurs if the video dma requests cannot be serviced fast enough by the memory subsystem. in this case, halt is asserted and the video baud clock is stopped, such that video data will momentarily be stopped from being sent to the lcd. the freezeframe condition is asserted in response to the assertion of the enfreezeframe control bit. this causes the video baud clock to stop and the video to stop shifting cleanly at the end of the current frame. the actual cp clock signal is generated by gating the video baud clock with the valid shift period, as determined by the count output of the horizontal counter. the clock used to shift the video output data also depends on the display type (4-bit split, 4-bit non-split, or 8-bit non split), since the 4-bit split and 8-bit non split types require data to be shifted as twice the cp rate such that an external register can be used to demultiplex the 4-bit data into the desired 8 parallel data lines. the video line rate and load pulse frequency is controlled by the video rate counter, which is preloaded with the vidrate[9:0] control register setting. this counter generates the load pulse by counting the programmed number of video baud clocks. in addition, setting the loaddly control bit will result in an additional baud clock delay to be inserted for the frame and cp signals with respect to the load signal, as shown in figure 17.3.2. some lcd?s may require this timing restriction. the toggle rate of the df signal is controlled by the df counter, which is preloaded with the dfval[7:0] control register setting. the df counter will count each time a load pulse is generated. if the dfmode control bit is set to logic ?0?, the df signal is configured to toggle on every frame. if the dfmode control bit is set to logic ?1?, the df signal is configured to toggle every time the df counter rolls over. the frame pulse generation is controlled by both the horizontal counter and line counter (see sections 17.3.3 and 17.3.4). together, these counters determine the video frame rate. the frame pulse is asserted for a duration of the entire first line at a frequency of once per frame. www.datasheet.in chapter 17 video module 17-10 vdat[3:0] cp load df frame load timing with loaddly = 1 (one baud clock delay) load timing with loaddly = 0 (no delay) vdat[3:0] cp load df frame figure 17.3.2 loaddly timing the video state machine also generates the video dma request signals used to fetch the video image data from memory. each data fetch sequence consists of one dma request followed by 4 successive video dma transactions, since video dma data transfers are busted as 4 longwords (32 bits each) at a time from system memory to the fifo buffers within the video module. the video dma requests are initiated whenever the fifo buffers are available to accept more data (see section 17.3.6). 17.3.3 horizontal counter the horizontal counter is used to count the number of bits that are shifted (in a burst fashion) into the lcd?s line shift register. for each new line, the horizontal counter is preloaded with the horzval[8:0] control register setting and counts each time the 4 bits (or 8 bits for 8-bit non-split lcd?s) of video output data are shifted out. the horzval value should equal the horizontal size of the lcd divided by 4 (or 8 for 8-bit non-split lcd?s) ? 1. thus, the 9-bit horizontal counter supports a maximum horizontal size of 2048 pixels. each time the video rate counter reaches it?s terminal count, the video state machine asserts the load pulse in order to transfer the entire line shift register contents to the lcd panel. thus, the video rate counter preload value vidrate[9:0] should be configured with a value greater than the horizontal counter preload value horzval[8:0] in order to load the entire line shift register contents to the lcd after all the bits have been shifted into the line shift register. figure 17.2.3 shows an example of the relative timing for the load pulse versus the burst of cp clocks used to shift a horizontal line of data. www.datasheet.in chapter 17 video module 17-11 17.3.4 line counter the line counter is used to count the number of lines that are displayed by the lcd. each time the line counter reaches it?s terminal count, the video state machine asserts the frame pulse in order to begin a new frame and cause the pointers in the lcd to return to the top of the display. for each new frame, the line counter is preloaded with the lineval(9:0) control register setting and counts each time a load pulse is generated. the lineval value should equal the number of lines for the lcd ? 1. the 10-bit line counter supports a maximum vertical size of 1024 lines. 17.3.5 dma address generation the dma address generation circuit consists of logic which generates the address for fetching video data from the video buffer located in system memory. the video buffer can be relocated anywhere in memory (over the full 32-bit address space) by configuring the vidbank[31:20], vidbasehi[19:4], and vidbaselo[19:4] control register settings. see figure 17.3.3 for a block diagram of the video dma address generation circuit. for a split lcd, the vidbank and vidbasehi bits are concatenated to provide the start address for the upper (hi) portion of the video buffer, while the vidbank and vidbaselo bits are concatenated to provide the start address for the lower (lo) portion of the video buffer. for a non-split lcd, the vidbank and vidbasehi bits are concatenated to provide the start address for the video buffer. cnt load logic 16 16 16 16 12 12 control from cpu dma addr video vidaddlo[19:4] 2:1 mux cmp vidaddhi[19:4] hi addr cnt hi/lo select (split mode) vidbasehi cntl reg vidbank cntl reg vidbaselo cntl reg lo addr cnt 16 figure 17.3.3 video dma address generation www.datasheet.in chapter 17 video module 17-12 the dma address generation circuit consists of 2 sets of counters, the hi address counter and the lo address counter, which generate the address for the hi and lo portions of the video buffer, respectively. both of these counters are incremented whenever the video fifo buffer is filled from a burst of dma-initiated data transfers. for a split lcd, the vidbank and vidaddhi bits are concatenated to provide the address for the upper (hi) portion of the video buffer, while the vidbank and vidaddlo bits are concatenated to provide the address for the lower (lo) portion of the video buffer. a 2:1 multiplexer is used to select between these two combined addresses, depending on whether the current video data fetch is for a hi or lo portion of the buffer. for a non-split lcd, the vidbank and vidaddhi bits are concatenated to provide the address for the video buffer. figure 17.3.4 shows the dma address fields for split and non-split display formats. video data is fetch as a burst of 4 longwords at a time and takes advantage of the fast-page mode available for dram or sdram. split display 313029282726252423222120191817161514131211109876543210 vidbank[31:20] vidaddhi[19:4] 0 0 0 0 313029282726252423222120191817161514131211109876543210 vidbank[31:20] vidaddlo[19:4] 0 0 0 0 non-split display 313029282726252423222120191817161514131211109876543210 vidbank[31:20] vidaddhi[19:4] 0 0 0 0 figure 17.3.4 video dma address fields the vidbank control bits provide a bank location for the video buffer. the video bank can be located anywhere in memory over the full 32-bit address space, in increments of 1 mbyte. these bits are latched at the beginning of each frame, making it possible to change these bits while the video module is active and have the video address switch to the new bank at the start of the next frame. in addition, the video buffer start address can be located anywhere within the 1 mbyte bank, in increments of 16 bytes. the hi and lo address counters are both up-counters. thus, vidbasehi must be configured to a lower value than vidbaselo. the hi and lo address counters are reloaded with the vidbasehi and vidbaselo values, respectively, whenever the hi address counter output vidaddhi equals the vidbaselo value. therefore, vidbaselo value must always be set to one address greater than the end address of the upper (hi) portion of the display. for non-split displays, the vidbaselo value must always be set to one address greater than the end address of the display. www.datasheet.in chapter 17 video module 17-13 17.3.6 video fifo the video module contains several sets of first-in first-out (fifo) buffers to support video dma burst data transfers. as shown in figure 17.3.1, these fifos are organized as 4 sets of fifos. each set of fifos is further subdivided into 4 latches (4 32-bits or a total of 128 bits wide). the first set of fifos is referred to as fifoa. video data is loaded one longword (32 bits) at a time from the memory subsystem consecutively into each of the 4 latches of fifoa. fifoa then feeds both fifob and fifolo, while fifob feeds fifohi, with all of these data transfers performed 128 bits in parallel at a time. for example, the 1st latch of fifoa directly loads into the 1st latch of fifob, at the same time the 2nd latch of fifoa directly loads into the 2nd latch of fifob, etc. fifohi and fifolo are used to separately buffer the video data for the upper (hi) and lower (lo) portions of a split display, if this mode is enabled. for a non-split display, fifolo is not used. in this mode, fifoa accepts and buffers the 4-longword burst of data from the memory subsystem. whenever fifoa is full, and fifob is empty, the 4 longwords from fifoa will then be transferred to fifob. similarly, whenever fifoa is full again and fifob is full, and fifohi is empty, the 4 longwords from fifob will then be transferred to fifohi. then, the data is emptied from fifohi one longword at a time as the data is fetched for eventual shifting out to the lcd. for a split display, both fifohi and fifolo are used. in this mode, fifoa accepts and buffers the 4-longword burst of data from the memory subsystem. whenever fifoa is full, and fifob is empty, the 4 longwords from fifoa will then be transferred to fifob. then whenever fifoa and fifob are both full, and fifohi and fifolo are both empty, the 4 longwords from fifob will then be transferred to fifohi at the same time the 4 longwords from fifoa are transferred to fifolo. this is the mechanism used for separately buffering the video data for the upper (hi) and lower (lo) portions of the split display. as explained in the previous section, the video dma address generation logic ensures that the correct hi or lo buffer address is generated at the correct time. finally, the data is emptied from fifohi or fifolo one longword at a time via a multiplexer array, based on whether the current output cycle corresponds to an upper or lower portion of the split display. www.datasheet.in chapter 17 video module 17-14 17.3.7 gray scale lut the video module supports monochrome, 4-level or 16-level gray scale, and 8-bit per pixel color modes. the gray scale and color modes are implemented using a programmable lookup table (lut) for selecting the shades of gray or color, followed by a programmable time-based dithering algorithm in the dither selector circuit. the monochrome mode bypasses these circuits and basically serializes the fifohi (and fifolo if a split display is used) output data into 4-bit streams for shifting to the lcd. the gray scale modes of the video module are implemented by varying the duty cycle (i.e., number of frames) for which a given pixel is turned on, giving the monochrome display an appearance of gray scale. in order to reduce the noticeable flicker caused by turning on and off adjacent pixels at the same time, a time-based dithering algorithm is used. two gray scale modes are supported by the video module: 2-bit gray (4-level) or 4-bit gray (16- level). since the lut used in the video module consists of 16 total entries or gray scales, the 4-bit gray scale processing path does not require a lut (all 16 gray scales are available and used in this mode). the 4-bit gray scale mode requires that the number of bits stored in the video buffer is equal to 4 times the number of pixels, with each pixel corresponding to 4 consecutive data bits stored in the video buffer. each set of these 4 gray scale bits maps to one pixel of dithered data generated by the dither selector. the 2-bit gray mode does use a lut, which allows any 4 gray levels to be selected out of the 16 total possible gray levels. the 2-bit gray scale mode requires that the number of bits stored in the video buffer is equal to 2 times the number of pixels, with each pixel corresponding to 2 consecutive data bits stored in the video buffer. the 2-bit gray scale lut uses the bluesel[15:0] control bits as the programmable lut entries. the 16-bit bluesel field is divided into 4 nibbles: bluesel[15:12], bluesel[11:8], bluesel[7:4], and bluesel[3:0]. each nibble then corresponds to one of the 4 gray scales selected out of 16 possible, with each 2 pre-gray-scale bits from memory used to lookup one of these 4 gray scales at a time (2 to 4 mapping). figure 17.3.5 shows a block diagram of the 2-bit gray scale lut logic. each set of the 4 gray scale bits from the lut output maps to one pixel of dithered data generated by the dither selector. 2 3 1 0 4 2 16 2-bit pre-grey scale raw data (from memory) 2-bit post-grey scale data bluesel[15:0] [11:8] [7:4] [3:0] [15:12] sel lut (4) 4:1 mux figure 17.3.5 2-bit gray scale lut www.datasheet.in chapter 17 video module 17-15 17.3.8 color lut the video module supports an 8-bit per pixel color mode for interfacing to color lcd?s. the color mode generates 16 different shades using the time-based dithering algorithm. the 8-bits used per pixel are encoded into 3 bits of red (r), 3 bits of green (g), and 2 bits of blue (b). the color mode requires that 8 bits (3:3:2 for r:g:b) are stored in the video buffer for every rgb-tri (one pixel) of dithered data shifted to the color lcd. the color mode uses separate luts for red, green, and blue. the red lut uses the redsel[31:0] control bits as the programmable lut entries. the 32-bit redsel field is divided into 8 nibbles: redsel[31:28], redsel[27:24], ? , redsel[7:4], and redsel[3:0]. each nibble then corresponds to one of the 8 shades selected out of 16 possible, with each 3 pre-red bits from memory used to lookup one of these 4 shades at a time (3 to 4 mapping). the green lut is identical to the red lut, except the lut uses the greensel[31:0] control bits as the programmable lut entries. the blue lut uses the bluesel[15:0] control bits as the programmable lut entries, and each lut output nibble corresponds to one of the 4 shades selected out of 16 possible, with each 2 pre-blue bits from memory used to lookup one of these 4 shades at a time (2 to 4 mapping). figure 17.3.6 shows a block diagram of the 8-bit per pixel color lut logic. www.datasheet.in chapter 17 video module 17-16 4 7 [31:28] [27:24] [23:20] [19:16] [15:12] [11:8] [7:4] [3:0] 6 5 4 3 2 1 0 sel ( 4 ) 8:1 mux 3 4 7 [31:28] [27:24] [23:20] [19:16] [15:12] [11:8] [7:4] [3:0] 6 5 4 3 2 1 0 sel ( 4 ) 8:1 mux 3 4 [15:12] [11:8] [7:4] [3:0] 3 2 1 0 sel (4) 4:1 mux 2 32 32 16 color lut post-red data post-blue data post-green data 3-bit pre-red raw data (from memory) 2-bit pre-blue raw data (from memory) 3-bit pre-green raw data (from memory) bluesel[15:0] greensel[31:0] redsel [ 31:0 ] figure 17.3.6 8-bit per pixel color lut www.datasheet.in chapter 17 video module 17-17 17.3.9 dithering the dither selector is based on a scheme which varies the duty cycle (i.e., number of frames) for which a given pixel is turned on, giving the display an appearance of multiple shades. in order to reduce the noticeable flicker caused by turning on and off adjacent pixels at the same time, a time-based dithering algorithm is used to vary the pattern of adjacent pixels every frame. a block diagram of the dither selector is shown in figure 17.3.7. the dither selector contains a set of dithering line counters and a set of dithering frame counters. the set of dithering line counters contains 4 counters which count modulo-3, modulo-4, modulo-5, and modulo-7 every horizontal line. the set of dithering frame counters contains 4 counters which count modulo-3, modulo-4, modulo-5, and modulo-7 each video frame. the output of the dithering line counters are used to lookup the programmable dither patterns configured in video control registers 8 through 14, generating a 16-bit enable pattern. each new line count looks up a different field of the appropriate video control register, resulting in a time-varying and dithered pattern of on and off pixel control with the desired duty cycle. section 17.4 lists recommended values for each of these dither patterns. the pre-dithered video data is processed by sending 16 adjacent bits at a time through 4 identical enable select circuits, each of which processes 4 bits of pre-dithered data. each 4 bits of pre-dithered data is used to lookup one of the 16 possible enable patterns, which thus determine whether or not a given pixel is turned on or off for the given frame and line. thus every 4 bits of pre-dithered data produces 1 bit of dithered data. table 17.3.1 shows the duty cycle ratios used by the enable select circuits, which correspond to the 16 possible shades (of gray or color) available. table 17.3.1 dither duty cycles pre-dithered data nibble duty cycle 15 1 14 6/7 13 4/5 12 3/4 11 5/7 10 2/3 93/5 84/7 72/4 63/7 52/5 41/3 32/7 21/5 11/7 00 www.datasheet.in chapter 17 video module 17-18 dithering frame counters dithering line counters enable lut 2 mod-3 mod-4 mod-5 mod-7 2 3 3 164 bit 16 4 4 4 4 1 1 1 1 1 enable select enable select enable select 16-bit pre-dither data 4-bit post-dither data (1 nibble of video pixels) enable select enable patterns prgm dither patterns (from video control 8~14 registers) figure 17.3.7 dither selector block diagram 17.3.10 related interrupts lcdint: issues an interrupt at the end of each video frame. dfint: issues an interrupt each time the video df signal toggles. www.datasheet.in chapter 17 video module 17-19 17.4 video registers 17.4.1 video control 1 register offset = $028: bit label reset read/write 31-22 linecnt[9:0] 0 r 21 loaddly 0 r/w 20-16 baudval[4:0] x r/w 15-9 viddoneval[16:0] x r/w 8 enfreezeframe 0 r/w 7-6 bitsel[1:0] 0 r/w 5 dispsplit 0 r/w 4disp8 0 r/w 3dfmode 0 r/w 2 invvid 0 r/w 1dispon 0 r/w 0envid 0 r/w linecnt[9:0]: read-only these bits provide the status of the line counter. loaddly: setting this bit will cause the frame and cp signals to be delayed by an additional baud clock relative to the load signal. this is only required by some kinds of lcds that have a long specification time between load and cp. baudval[4:0]: these bits determine the rate of the cp clock. these bits must be set to a minimum of $1 and should be set to as high a value as possible to interface to the selected lcd. the following equation provides clock rate: cp rate = 2 2 0] : baudval[4 f vidclk + * viddoneval[6:0] these bits determine the time between the end of video shifting and the assertion of viddone signal. these bits must be set to at least a valve of $1. setting those bits to a valve of $1 will cause a delay from the video finishing shifting to the assertion of viddone of six clk periods (normally 162 ns). each increment to these bits will provide an additional 16 clk periods (normally 434 ns). enfreezeframe: setting this bit will cause the video logic to freeze at the end of the current frame. this feature is used to blip a single frame. the video logic will not start transferring data again until this bit is cleared and the envid bit is toggled. www.datasheet.in chapter 17 video module 17-20 bitsel[1:0]: these bits define the bit depth for the video module to generate according to the following: $3 8-bit per pixel color mode $2 4-bit per pixel gray scale mode $1 2-bit per pixel gray scale mode $0 monochrome mode dispsplit: this bit should be set if interfacing to a split lcd. disp8: this bit should be set if interfacing to an 8-bit non-split lcd. dfmode: if this bit is a logic ?0? then the df signal will be toggled on each frame. if this bit is a logic ?1? then the df signal will toggle at the rate defined by the dfval (7:0) bits. invvid: setting this bit will cause the vdat[3:0] signals to be inverted. dispon: this bit is directly connected to the dispon signal pin. envid: setting this bit will enable the video logic. this bit should not be set until all other control bits are setup. www.datasheet.in chapter 17 video module 17-21 17.4.2 video control 2 register offset = $02c: write-only bit label reset read/write 31-22 vidrate[9:0] x w 21 reserved 20-12 horzval[8:0] x w 11-10 reserved 9-0 lineval[9:0] x w vidrate[9:0]: write-only these bits determine the frequency at which the load pulse is generated, which in turn sets the frame rate. the line rate and frame rate are given by the following equations: line rate = 1 0] : vidrate[9 rate cp + frame rate = 1 0] : lineval[9 rate line + horzval[8:0]: write-only these bits define the horizontal size of the lcd according to the following equation: horzval = (horzsize 4 ? 1) for 4-bit split or non-split lcd horzval = (horzsize 8 ? 1) for 8-bit non-split lcd lineval[9:0]: write-only these bits define the number of lines for the lcd. lineval = (#of lines ? 1) for a non-split lcd lineval = (#of lines 2 ? 1) for a split lcd 17.4.3 video control 3 register offset = $030: write-only bit label reset read/write 31-20 vidbank[31:20] x w 19-4 vidbasehi[19:4] x w 3-0 reserved vidbank[31:20]: write-only these bits provide the upper bits of the address from which video data is fetched from memory. these bits are concatenated with the upper and lower address counters to provide the actual address. these bits are latched at the beginning of each frame, thus it is possible to change these bits ?on the fly? and the address will not change until the beginning of the next frame. vidbasehi[19:4]: write-only these bits provide the start address for the upper address counter. www.datasheet.in chapter 17 video module 17-22 17.4.4 video control 4 register offset = $034: write-only bit label reset read/write 31-24 dfval[7:0] x w 23-20 framemaskval[3:0] x w 19-4 vidbaselo[19:0] x w 3-0 reserved dfval[7:0]: write-only these bits define the rate at which the df signal will toggle if the dfmode bit is set. the df counter counts on each load pulse, thus the df rate is given by the following equation: df rate = 1 0] : dfval[7 rate line + vidbaselo[19:4]: write-only these bits provide the start address for the lower address counter. if a non-split lcd is used, these bits must be set to ?1? plus the last address of the video buffer. framemaskval[3:0]: these bits determine the number of lines for which the viddone signal will not assert following the assertion of the frame signal. if these bits are set to $0 then the viddone signal will assert after every line completes shifting. setting these bits to $1 will cause the viddone signal to not assert after the line that immediately follows the assertion of the frame signal. increases in these bits will cause subsequent lines to not assert the viddone signal. use of these bits allows the viddone synchronization pulses to be generated away torn the periods after the video fram and df transitions occur. www.datasheet.in chapter 17 video module 17-23 17.4.5 video control 5 register offset = $038: write-only bit label reset read/write 31-0 redsel[31:0] x w redsel[31:0]: write-only the video module logic generates 16 different shades using a time-based dithering algorithm. the 8-bit per pixel color mode encodes 3 bits of red, 3 bits of green, and 2 bits of blue. these bits define which of the sixteen shades each of the 8 possible red combinations will choose. in other words, 3 bits are expanded into 4 bits using these values as the lookup table. 3-bit pre-red data 4-bit post-red data 111 redsel[31:28] 110 redsel[27:24] 101 redsel[23:20] 100 redsel[19:16] 011 redsel[15:12] 010 redsel[11:8] 001 redsel[7:4] 000 redsel[3:0] 17.4.6 video control 6 register offset = $03c: write-only bit label reset read/write 31-0 greensel[31:0] x w greensel[31:0]: write-only the video module logic generates 16 different shades using a time-based dithering algorithm. the 8-bit per pixel color mode encodes 3 bits of red, 3 bits of green, and 2 bits of blue. these bits define which of the sixteen shades each of the 8 possible green combinations will choose. in other words, 3 bits are expanded into 4 bits using these values as the lookup table. 3-bit pre-green data 4-bit post-green data 111 greensel[31:28] 110 greensel[27:24] 101 greensel[23:20] 100 greensel[19:16] 011 greensel[15:12] 010 greensel[11:8] 001 greensel[7:4] 000 greensel[3:0] www.datasheet.in chapter 17 video module 17-24 17.4.7 video control 7 register offset = $040: rite-only bit label reset read/write 31-16 reserved 15-0 bluesel[15:0] x w bluesel[15:0]: write-only the video module logic generates 16 different shades using a time-based dithering algorithm. the 8-bit per pixel color mode encodes 3 bits of red, 3 bits of green, and 2 bits of blue. these bits define which of the sixteen shades each of the 4 possible blue combinations will choose. in other words, 2 bits are expanded into 4 bits using these values as the lookup table. the bluesel values are also used as the lut for the 2-bit gray scale mode. 2-bit pre-blue data 4-bit post-blue data 11 bluesel[15:12] 10 bluesel[11:8] 01 bluesel[7:4] 00 bluesel[3:0] 17.4.8 video control 8 register offset = $044: write-only bit label reset read/write 31-12 reserved 11-0 pat2_3l[11:0] x w pat2_3 [11:0]: write-only these bits define the (2 out of 3) patterning for the dithering algorithm. the (1 out of 3) patterning for the dithering algorithm is the inverse of the (2 out of 3) patterning. line pattern field recommended pattern 0 pat2_3[11:8] 0111 1 pat2_3[7:4] 1101 2 pat2_3[3:0] 1010 www.datasheet.in chapter 17 video module 17-25 17.4.9 video control 9 register offset = $048: write-only bit label reset read/write 31-16 pat3_4[15:0] x w 15-0 pat2_4[15:0] x w pat3_4[15:0]: write-only these bits define the (3 out of 4) patterning for the dithering algorithm. line pattern field recommended pattern 0 pat3_4[15:12] 0111 1 pat3_4[11:8] 1101 2 pat3_4[7:4] 1011 3 pat3_4[3:0] 1110 pat2_4[15:0]: write-only these bits define the (2 out of 4) patterning for the dithering algorithm. line pattern field recommended pattern 0 pat2_4[15:12] 1010 1 pat2_4[11:8] 0101 2 pat2_4[7:4] 1010 3 pat2_4[3:0] 0101 www.datasheet.in chapter 17 video module 17-26 17.4.10 video control 10 register offset = $04c: write-only bit label reset read/write 31-20 reserved 19-0 pat4_5[19:0] x w pat4_5[19:0]: write-only these bits define the (4 out of 5) patterning for the dithering algorithm. the (1 out of 5) patterning for the dithering algorithm is the inverse of the (4 out of 5) patterning. line pattern field recommended pattern 0 pat4_5[19:16] 0111 1 pat4_5[15:12] 1101 2 pat4_5[11:8] 1111 3 pat4_5[7:4] 1011 4 pat4_5[3:0] 1110 17.4.11 video control 11 register offset = $050: write-only bit label reset read/write 31-20 reserved 19-0 pat3_5[19:0] x w pat3_5[19:0]: write-only these bits define the (3 out of 5) patterning for the dithering algorithm. the (2 out of 5) patterning for the dithering algorithm is the inverse of the (3 out of 5) patterning. line pattern field recommended pattern 0 pat3_5[19:16] 0111 1 pat3_5[15:12] 1010 2 pat3_5[11:8] 0101 3 pat3_5[7:4] 1010 4 pat3_5[3:0] 1101 www.datasheet.in chapter 17 video module 17-27 17.4.12 video control 12 register offset = $054: write-only bit label reset read/write 31-28 reserved 27-0 pat6_7[27:0] x w pat6_7(27:0): write-only these bits define the (6 out of 7) patterning for the dithering algorithm. the (1 out of 7) patterning for the dithering algorithm is the inverse of the (6 out of 7) patterning. line pattern field recommended pattern 0 pat6_7[27:24] 1111 1 pat6_7[23:20] 1011 2 pat6_7[19:16] 1111 3 pat6_7[15:12] 1101 4 pat6_7[11:8] 1111 5 pat6_7[7:4] 1110 6 pat6_7[3:0] 0111 17.4.13 video control 13 register offset = $058: write-only bit label reset read/write 31-28 reserved 27-0 pat5_7[27:0] x w pat5_7[27:0]: write-only these bits define the (5 out of 7) patterning for the dithering algorithm. the (2 out of 7) patterning for the dithering algorithm is the inverse of the (5 out of 7) patterning. line pattern field recommended pattern 0 pat5_7[27:24] 0111 1 pat5_7[23:20] 1011 2 pat5_7[19:16] 0101 3 pat5_7[15:12] 1010 4 pat5_7[11:8] 1101 5 pat5_7[7:4] 1110 6 pat5_7[3:0] 1111 www.datasheet.in chapter 17 video module 17-28 17.4.14 video control 14 register offset = $05c: write-only bit label reset read/write 31-28 reserved 27-0 pat4_7[27:0] x w pat4_7[27:0]: write-only these bits define the (4 out of 7) patterning for the dithering algorithm. the (3 out of 7) patterning for the dithering algorithm is the inverse of the (4 out of 7) patterning. line pattern field recommended pattern 0 pat4_7[27:24] 1011 1 pat4_7[23:20] 1001 2 pat4_7[19:16] 1101 3 pat4_7[15:12] 1100 4 pat4_7[11:8] 0110 5 pat4_7[7:4] 0110 6 pat4_7[3:0] 0011 www.datasheet.in chapter 18 electrical characteristics 18-1 18. electrical characteristics 18.1 electrical characteristics of TMPR3911bu/bxb 18.1.1 absolute maximum ratings (TMPR3911bu/bxb) v ss = 0 v (gnd) parameter symbol rating unit supply voltage (i/o) v dd v ss ? 0.5 to 4.5 v supply voltage (internal logic) v ddl v ss ? 0.5 v ddh v input voltage v in v ss ? 0.5 to v ddh + 0.5 v storage temperature t stg ? 55 to 125 c maximum dissipation (ta = 70 c) p d 1w note: using an lsi at specifications higher than the maximum ratings can cause permanent damage to the lsi. for normal operation, use under the recommended operating conditions. exceeding the recommended operating conditions may affect the reliability of the lsi. 18.1.2 recommended operating conditions (TMPR3911bu/bxb) v ss = 0 v (gnd) parameter symbol condition min typ. max unit power supply voltage v ddh 3.0 3.3 3.6 v power supply voltage v ddl 2.4 2.6 2.8 3.3 v ih1 v ddh = 3.6 v v ddh 0.8 ? v ddh + 0.3 v input voltage ( * 1) v il1 v ddh = 3.0 v ? 0.3 ? v ddh 0.1 v v ih2 v ddh = 3.6 v 2.4 ? v ddh + 0.3 v input voltage ( * 2) v il2 v ddh = 3.0 v ? 0.3 ? 0.6 v sysclk input frequency f sysclk 4.5 ? 7.3728 mhz c32k input frequency f 32k ? 32.768 ? khz operating temperature t opr ? 20 ? 70 c ( * 1) sysclkin, dclkin, mbusint ( * 2) other inputs www.datasheet.in chapter 18 electrical characteristics 18-2 18.1.3 dc characteristics (TMPR3911bu/bxb) (ta = ? 20 c to 70 c, v ddh = 3.3 v 0.3 v, vddl = 2.6 v 0.2 v) parameter symbol condition min typ. max unit idd vddh ? 45 50 operating current (1) idd vddl v in = v ddh or v ss i oh = i ol =0 ma f sysclk = 7.3728 mhz 88 95 ma iddd vddh ? 15 20 doze mode current (2) iddd vddl v in = v ddh or v ss i oh = i ol = 0 ma f sysclk = 7.3728 mhz ? 30 35 ma idds1 vddh ? 110 sleep mode current (3) idds1 vddl v in = v ddh or v ss i oh = i ol = 0 ma ? 19 110 a idds2 vddh ? 110 static current (4) idds2 vddl v in = v ddh or v ss i oh = i ol = 0 ma ? 990 a input leakage current i in v in = v ddh or v ss ? 10 ? 10 a v oh1 v ddh = 3.0 v, i oh = ? 4 ma v dd ? 0.6 ?? v output voltage (5) v ol1 v ddh = 3.0 v, i ol = 4 ma ??+ 0.4 v v oh2 v ddh = 3.0 v, i oh = ? 8 ma v dd ? 0.6 ?? v output voltage (6) v ol2 v ddh = 3.0 v, i ol = 8 ma ??+ 0.4 v v oh3 v ddh = 3.0 v, i oh = ? 16 ma v dd ? 0.6 ?? v output voltage (7) v ol3 v ddh = 3.0 v, i ol = 16 ma ? ?+ 0.3 v v oh4 v ddh = 3.0 v, i oh = ? 24 ma v dd ? 0.6 ?? v output voltage (8) v ol4 v ddh = 3.0 v, i ol = 24 ma ??+ 0.4 v input current (pull-down resistor) i ihp v dd = max v in = v dd 20 ? 120 a (1) based on toshiba original benchmark program measurement. (2) cpu is stopped (stopspu = 1). internal peripherals are running. (3) rtc is running. internal peripherals are stopped. (4) rtc is stopped. internal peripherals are stopped. (5) d[31;0], ras0*, ras1*, dcs0*, dcke, dqmh, dqml, dreq*, dgrnt*, bc32k, vdat[3:0], cp, load, df, frame, dispon, viddone, pwrcs, txd, rxd, cs3*-cs0*, chifs, chiclk, chidout, chidin, io[6;0], spiclk, spiout, spiin, sibsync, sibdout, sibmclk, sibclk, rxpwr, irout, card1wait*, card2wait*, miox[2:0] (6) a[12:0], ale, rd*, we*, cas3*-cas0*, cardreg*, cardiowr*, cardiord*, card1csl*, card1csh*, card2csl*, card2csh* (7) dclkout (8) mbusclk, mbusdata www.datasheet.in chapter 18 electrical characteristics 18-3 18.1.4 crystal oscillator characteristics (TMPR3911bu/bxb) 18.1.4.1 crystal oscillator conditions (1) 7.3728 mhz crystal recommended value parameter symbol min max unit crystal oscillator frequency f in 4.5 7.3728 mhz external capacitors c in , c out 10 33 pf (2) 32.768 khz crystal recommended value parameter symbol min max unit external capacitors c in , c out 10 33 pf 18.1.4.2 electrical specifications (v ss = 0 v, v dd = 3.3 v) parameter symbol condition min typ. max unit crystal stabilization time 7.3728 mhz t sta-59m t.b.d. ?? t.b.d. ms crystal stabilization time 32 khz t sta-32k t.b.d. ?? t.b.d. s c out c in x?tal sysclkout sysclkin TMPR3911bu/bxb c in recommended 32.768 khz crystal kyocera corporation: kf-38g c32kout c32kin TMPR3911bu/bxb x?tal c out www.datasheet.in chapter 18 electrical characteristics 18-4 18.1.5 TMPR3911bu/bxb timing hold v ddh 0.5 delay setup 0.8v cc 0.2v cc outputs inputs v ddh 0.5 v ddh 0.5 + 0.1 v v ddh 0.5 ? 0.1 v v ddh 0.5 v ddh 0.5 www.datasheet.in chapter 18 electrical characteristics 18-5 18.1.6 ac characteristics (TMPR3911bu/bxb) the following operating conditions apply to all values specified in this section. t a = ? 20 oc to 70 oc, v ddh = 3.3 0.3 v, v ddl = 2.6 0.2 v, external capacitance = 40 pf chapter 18 electrical characteristics 18-6 symbol parameter calculation t 44 address valid to ale falling edge t 3 + t 5 ? t 6 t 45 ale falling edge to address hold t 3 + t 6 ? t 5 t 46 access time for read 2 * accval1 * t 3 ? (t 10 or t 38 ) ? (t 39 or t 41 ) t 47 write pulse width 2 * accval1 * t 3 + t 13 or t 14 t 48 address valid to csx/mcsx * falling edge at least t 3 ? t 6 + (t 10 or t 38 ) t 49 address valid to we * falling edge t 3 ? t 6 + t 14 t 50 data valid to we * rising edge 2 * accval1 * t 3 + t 3 ? (t 7 or t 8 ) + t 13 t 51 we * rising edge to data hold at least t 3 t 52 access time for 2nd/3rd/4th read 2 * accval2 * t 3 + t 3 ? t 6 ? (t 39 or t 41 ) t 53 access time for read (card) 2 * ((2 * cardxaccval) ? 1) * t 3 ? t 18 ? t 39 t 54 address valid to cardcs * falling edge 3 * t 3 ? t 6 + t 18 t 55 write pulse width (card) 2 * ((2 * cardxaccval) ? 1) * t 3 + t 13 ? t 14 t 56 data valid to we * rising edge (card) 2 * ((2 * cardxaccval) ? 1) * t 3 + 3 * t 3 ? t 7 + t 13 t 57 we * rinsing edge to data hold(card) at least t 3 t 58 data valid to iowr * rising edge 2 * ((2 * cardioxaccval) ? 1) * t 3 + 3 * t 3 ? t 7 + t 25 t 59 iowr * rinsing edge to data hold at least t 3 t 60 iowr * pulse width 2 * ((2 * cardxioaccval) ? 1) * t 3 ? 2 * t 3 ? t 25 ? t 26 t 61 ras * falling edge to cas * falling edge (4 or 6) * t 3 + t 16 ? (t 28 or t 30 ) t 62 address valid to ras * falling edge t 3 + (t 28 or t 30 ) ? t 6 t 63 address valid to cas * falling edge t 3 + t 16 ? t 6 t 64 cas * pulse width (1 or 2) * t 3 + t 15 ? t 16 t 65 data valid to cas * rising edge (4 or 5) * t 3 + t 15 ? (t 7 or t 8 ) t 66 cas * rising edge to data hold at least t 3 t 67 control signal active to dcke t 3 + t 35 ? (delay for each signal) t 68 data valid to cas * rising edge (in-page) 3 * t 3 + t 15 ? (t 7 or t 8 ) t 69 access time for read (io card) 2 * ((2 * cardxioaccval) ? 1) * t 3 ? 2 * t 3 ? t 39 ? t 24 www.datasheet.in chapter 18 electrical characteristics 18-7 dclkout t 1 t 3 t 2 dclkout timing dclkout dclkin t 43 dclkout to dclkin timing www.datasheet.in chapter 18 electrical characteristics 18-8 cs/mcs device access timing(1) - write operation dclkout ale a[12:0] d[31:0] csx * /mcsx * we * wex * t 4 t 5 t 6 t 6 t 7 , t 8 t 10 , t 38 t 9 , t 37 t 14 t 16 t 13 t 15 t 44 t 50 t 49 www.datasheet.in chapter 18 electrical characteristics 18-9 cs/mcs device access timing(2) - read operation dclkout ale a[12:0] d[31:0] csx * /mcsx * rd * t4 t 5 t 6 t 6 t 10 ,t 38 t 9 ,t 37 t 12 t 11 t 39 .t 41 t 40 ,t 42 t 44 t 48 t 46 www.datasheet.in chapter 18 electrical characteristics 18-10 cs/mcs device access timing(3) - burst read operation with page mode enabled dclkout ale a[12:0] d[31:0] csx * /mcsx * rd * t 4 t 5 t 6 t 6 t 10 ,t 38 t 12 t 39 .t 41 t 40 ,t 42 t 39 .t 41 t 40 ,t 42 t 6 t 6 t 44 t 48 t 52 t 46 www.datasheet.in chapter 18 electrical characteristics 18-11 card device memory access timing(1) - write operation dclkout ale a[12:0] d[31:16] cardxcs * we * t 4 t 5 t 6 t 6 t 7 t 14 t 13 t 18 t 17 t 44 t 56 www.datasheet.in chapter 18 electrical characteristics 18-12 card device memory access timing(2) - read operation dclkout ale a[12:0] d[31:16] cardxcs * t 4 t 5 t 6 t 6 t 18 t 17 t 12 t 11 t 19 t 20 t 39 t 40 rd * carddir * t 44 t 54 t 53 www.datasheet.in chapter 18 electrical characteristics 18-13 card device i/o access timing(1) - write operation dclkout a le a [12:0] d[31:16] cardxcs * t 4 t 5 t 6 t 6 t 7 t 18 t 17 t 22 t 21 t 26 t 25 cardreg * iowr * t 58 www.datasheet.in chapter 18 electrical characteristics 18-14 card device i/o access timing(2) - read operation dclkout ale a[12:0] d[31:16] cardxcs * t 4 t 5 t 6 t 6 t 18 t 17 t 19 t 20 t 39 t 40 iord * carddir * cardreg * t 22 t 21 t 24 t 23 t 69 www.datasheet.in chapter 18 electrical characteristics 18-15 dclkout a[12:0] d[31:0] rasx * casx * we * t 6 t 6 t 7 , t 8 t 28 , t 30 t 16 t 14 t 15 t 27 , t 29 t 16 t 15 t 13 t 62 t 63 t 61 t 65 t 68 dram access timing(1) - write operation www.datasheet.in chapter 18 electrical characteristics 18-16 dram access timing(2) - read operation dclkout a[12:0] d[31:0] rasx * casx * we * t6 t6 t28,t30 t16 t15 t27,t29 t16 t15 t39,t41 t40,t42 t39,t41 t40,t42 t62 t63 www.datasheet.in chapter 18 electrical characteristics 18-17 dclkout a [12:0] d[15:0] t 6 t 6 t 8 t 34 , t 30 ras0 * cas0 * w e * t 28 t 16 t 14 t 15 t 13 t 27 t 27 t 28 t 33 , t 29 t 34 , t 30 t 33 , t 29 t 34 , t 30 t 33 , t 29 t 8 t 8 t 8 t 31 t 32 dcsx * dqml/dqmh sdram access timing(1) - write operation www.datasheet.in chapter 18 electrical characteristics 18-18 sdram access timing(2) - read operation dclkout a[12:0] d[15:0] t 6 t 6 t 34 ,t 30 ras0 * cas0 * we * t 28 t 16 t 14 t 15 t 13 t 27 t 2 7 t 28 t 33 ,t 29 t 34 ,t 30 t 33 ,t 29 t 34 ,t 30 t 33 ,t 29 dcsx * dqml/dqmh t 41 t 42 www.datasheet.in chapter 18 electrical characteristics 18-19 chapter 18 electrical characteristics 18-20 chi timing chiclk (output) t 1 t 5 t 6 t 3 chifs (output) (chitxfsedge=1) chidout (chitxedge=1) chidin (chitxedge=1) chiclk (input) chifs (input) (chifsedge=0) chidout (chitxedge=0) chidin (chitxedge=0) t 4 t 4 t 10 t 11 t 1 t 3 t 2 t 12 t 13 t 7 t 7 t 10 t 11 www.datasheet.in chapter 18 electrical characteristics 18-21 chapter 18 electrical characteristics 18-22 chapter 18 electrical characteristics 18-23 sib timing sibmclk sibsclk sibsync sibdout sibdin t 1 t 3 t 2 t 5 t 6 t 4 t 7 t 8 t 10 t 8 t 9 www.datasheet.in chapter 18 electrical characteristics 18-24 chapter 18 electrical characteristics 18-25 |
Price & Availability of TMPR3911
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |